Triple
T37091886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Texas State Highway 146 |
E918443
|
entity |
| Predicate | structureOnRoute |
P53579
|
FINISHED |
| Object | Fred Hartman Bridge |
E1194635
|
NE 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: Fred Hartman Bridge | Statement: [Texas State Highway 146, structureOnRoute, Fred Hartman Bridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: structureOnRoute Context triple: [Texas State Highway 146, structureOnRoute, Fred Hartman Bridge]
-
A.
routeStructure
Indicates the structural or organizational relationship between a route and its constituent segments, paths, or connections.
-
B.
laneStructure
Indicates the structural organization and configuration of lanes within a roadway or traffic facility.
-
C.
hasMajorStructureOnRoute
chosen
Indicates that a significant physical structure is located along or directly associated with a particular route.
-
D.
viaStructure
Indicates that one entity is connected to or accessed through a particular structural element or medium.
-
E.
structureOnSurface
Indicates that one entity is a structure physically situated on the surface of another entity.
- F. None of above.
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_69f76e9a48bc8190a3947508d8bca408 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb344c60f8819090f2e21e1e61d621 |
completed | May 6, 2026, 12:30 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41fd3e466481908340ec289ebc4491 |
completed | June 29, 2026, 5:06 a.m. |
| PD | Predicate disambiguation | batch_69fb2f642db08190b562725502c74ea6 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:14 p.m.