Triple
T5584168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 35W (Texas) |
E146712
|
entity |
| Predicate | hasParentRouteNumber |
P34375
|
FINISHED |
| Object | 35 |
—
|
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: 35 | Statement: [Interstate 35W (Texas), hasParentRouteNumber, 35]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParentRouteNumber Context triple: [Interstate 35W (Texas), hasParentRouteNumber, 35]
-
A.
hasRouteNumberingScheme
Indicates that one entity uses or is assigned a particular system or scheme for numbering its routes.
-
B.
hasPrimaryRoute
Indicates that one entity is designated as the main or principal route associated with another entity.
-
C.
isNumberedRouteIn
Indicates that a numbered route (such as a highway or road with an assigned number) is located within or passes through a specified geographic or administrative area.
-
D.
hasRouteIdentifier
chosen
Indicates that an entity is associated with a specific route code or identifier used to distinguish it from other routes.
-
E.
hasJunctionNumber
Indicates that a road, route, or similar pathway is assigned a specific junction or exit number.
- 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_69c0090287a08190b4098411effe970c |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c02084b5f0819089b62283c57704ec |
completed | March 22, 2026, 5:01 p.m. |
| PD | Predicate disambiguation | batch_69c01b16b9bc8190ab0b945507d90e05 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:37 p.m.