Triple
T2095506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 110 (Florida) |
E32770
|
entity |
| Predicate | northTerminusType |
P35918
|
FINISHED |
| Object | system interchange |
—
|
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: system interchange | Statement: [Interstate 110 (Florida), northTerminusType, system interchange]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: northTerminusType Context triple: [Interstate 110 (Florida), northTerminusType, system interchange]
-
A.
northernTerminusState
Indicates that a location or route has its northern endpoint or terminus within the specified state.
-
B.
isNorthernmostRegionOf
Indicates that one region is the geographically furthest north among all regions within a specified larger area or entity.
-
C.
terminusNorth
Indicates that one entity serves as the northern endpoint or final stop of another entity, such as a route, line, or path.
-
D.
locatedNorthOf
Indicates that one entity is positioned geographically to the north of another entity.
-
E.
locatedAtNorthernEndOf
Indicates that one entity is situated at or near the northernmost part or extremity of another entity.
- 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_69a885eba0708190999696a45cbec816 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abba99ddc48190bb2097b56efb7aca |
completed | March 7, 2026, 5:41 a.m. |
| PD | Predicate disambiguation | batch_69abb7b6274081909df36cd7a7c6a675 |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abba2e65b48190bb19cfc4b0f8c462 |
completed | March 7, 2026, 5:39 a.m. |
Created at: March 4, 2026, 7:43 p.m.