Triple
T33743606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kentucky telephone numbering plan area |
E864638
|
entity |
| Predicate | areaCodeOverlay |
P223
|
FINISHED |
| Object | 364 |
—
|
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: 364 | Statement: [Kentucky telephone numbering plan area, areaCodeOverlay, 364]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areaCodeOverlay Context triple: [Kentucky telephone numbering plan area, areaCodeOverlay, 364]
-
A.
hasAreaCodeOverlay
Indicates that a geographic area or phone number region shares multiple overlapping telephone area codes in the same service area.
-
B.
areaCode
chosen
Indicates that a location, phone number, or region is associated with a specific telephone area code.
-
C.
hasAreaCode
Indicates that a specified telephone area code is assigned to or associated with a particular geographic region, location, or phone service entity.
-
D.
hasAreaCodeType
Indicates that an entity’s area code is associated with a specific type or classification of area code.
-
E.
regionNumber
Indicates that an entity is assigned to or associated with a specific numbered region within a larger spatial or organizational division.
- 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_69f3498b24b8819096a65009e521d0e1 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5740fc81909774a4f65201a3ff |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:44 a.m.