Triple
T8744572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zion–Mount Carmel Tunnel |
E207790
|
entity |
| Predicate | parkRoadNumber |
P1864
|
FINISHED |
| Object | State Route 9 |
—
|
NE NERFINISHED |
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: State Route 9 | Statement: [Zion–Mount Carmel Tunnel, parkRoadNumber, State Route 9]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parkRoadNumber Context triple: [Zion–Mount Carmel Tunnel, parkRoadNumber, State Route 9]
-
A.
roadName
Indicates the specific name assigned to a road that identifies it within a transportation or address system.
-
B.
routeNumber
chosen
Indicates the specific identifying number assigned to a route within a transportation or delivery network.
-
C.
hasRoadNumberStatus
Indicates that a road or route is associated with a specific status regarding its assigned road number (e.g., active, reserved, retired, or provisional).
-
D.
hasConnectingRoadNumber
Indicates that there exists a road connection between two locations or road segments identified by a specific road number.
-
E.
roadServed
Indicates that a road is provided with necessary services or infrastructure support by a responsible entity.
- 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_69ca835bb2bc819084bb5906cb6ef7f8 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5d72e47c819099540d062d35ebd5 |
completed | March 31, 2026, 11:49 p.m. |
| PD | Predicate disambiguation | batch_69cc5c160dac8190b4aeb4bf0529de52 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:38 p.m.