Triple
T7695204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 275 (Tampa Bay) |
E174350
|
entity |
| Predicate | parentRouteNumber |
P78764
|
FINISHED |
| Object | 75 |
—
|
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: 75 | Statement: [Interstate 275 (Tampa Bay), parentRouteNumber, 75]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parentRouteNumber Context triple: [Interstate 275 (Tampa Bay), parentRouteNumber, 75]
-
A.
routeNumber
Indicates the specific identifying number assigned to a route within a transportation or delivery network.
-
B.
formerRouteNumber
Indicates that an entity previously had a specific route number before being renumbered, discontinued, or otherwise changed.
-
C.
parentRoute
Indicates that one route serves as the direct hierarchical ancestor or container of another route within a routing structure.
-
D.
primaryRouteType
Indicates the main category or kind of route associated with an entity, such as its primary mode, path, or routing classification.
-
E.
parentRouteType
Indicates that one route type serves as the parent or higher-level category for another route type within a route hierarchy.
- 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_69c6995966348190939e6c37ba272c06 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c706d1f0208190bc5b695aa5736244 |
completed | March 27, 2026, 10:38 p.m. |
| PD | Predicate disambiguation | batch_69c70163dea88190ae729df50e63dfd7 |
completed | March 27, 2026, 10:15 p.m. |
| PDg | Predicate description generation | batch_69c706d0c1708190a3e74523997814b8 |
completed | March 27, 2026, 10:38 p.m. |
Created at: March 27, 2026, 4:02 p.m.