Triple
T19747431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | area code 234 |
E474288
|
entity |
| Predicate | NANPCode |
P247
|
FINISHED |
| Object | 234 |
—
|
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: 234 | Statement: [area code 234, NANPCode, 234]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: NANPCode Context triple: [area code 234, NANPCode, 234]
-
A.
areaCode
Indicates that a location, phone number, or region is associated with a specific telephone area code.
-
B.
nationalPrefixForDomesticCalls
Indicates the dialing prefix that must be used when making domestic telephone calls within a given country or numbering plan.
-
C.
callingCode
chosen
Indicates the telephone country or area code associated with an entity for making phone calls.
-
D.
hasAreaCode
Indicates that a specified telephone area code is assigned to or associated with a particular geographic region, location, or phone service entity.
-
E.
mobileNumbersHaveNoGeographicAreaCode
Indicates that mobile phone numbers are not associated with or constrained by any specific geographic area code.
- 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_69d8e51940a0819087bd2996f98da668 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65295f3b88190a541354f41e3ea1d |
completed | April 20, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69e5305016e08190b9561a96baecb0b8 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:47 p.m.