Triple
T19747429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | area code 234 |
E474288
|
entity |
| Predicate | overlayType |
P137168
|
FINISHED |
| Object | geographic overlay |
—
|
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: geographic overlay | Statement: [area code 234, overlayType, geographic overlay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: overlayType Context triple: [area code 234, overlayType, geographic overlay]
-
A.
overlays
Indicates that one entity is placed on top of or superimposed over another, partially or completely covering it in the same spatial area.
-
B.
overlies
Indicates that one entity is positioned directly above and covering or resting on another entity, often with partial or complete contact.
-
C.
coversMode
Indicates that one entity includes, addresses, or supports a particular mode or manner of operation associated with another entity.
-
D.
overshadowedBy
Indicates that one entity’s importance, visibility, or impact is diminished because another entity is more prominent or dominant.
-
E.
ovalType
Indicates that one entity is classified as having an oval shape or belonging to an oval-shaped type.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69e532bbedf081908d801600e2af94a7 |
completed | April 19, 2026, 7:53 p.m. |
Created at: April 10, 2026, 1:47 p.m.