Triple
T28394011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South African telephone numbering plan |
E719233
|
entity |
| Predicate | localDialingRequiresAreaCode |
P148673
|
FINISHED |
| Object | true |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: true | Statement: [South African telephone numbering plan, localDialingRequiresAreaCode, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: localDialingRequiresAreaCode Context triple: [South African telephone numbering plan, localDialingRequiresAreaCode, true]
-
A.
localDialingWithoutAreaCodeAllowed
Indicates that local phone calls can be placed without dialing the area code.
-
B.
requiresAreaCodeForLocalCalls
chosen
Indicates that making local telephone calls in the given context necessitates dialing the area code.
-
C.
usesLeadingZeroInAreaCode
Indicates that an area code is written or represented with a leading zero before its significant digits.
-
D.
usesVariableLengthAreaCodes
Indicates that the telephone numbering plan in question employs area codes whose lengths are not fixed but can vary.
-
E.
hasAreaCode
Indicates that a specified telephone area code is assigned to or associated with a particular geographic region, location, or phone service entity.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69eff6efd1b08190ae3cefd4f11388a2 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 1:15 a.m.