Triple
T28640567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beaver, Utah |
E724909
|
entity |
| Predicate | secondaryAccessHighway |
P12245
|
FINISHED |
| Object | Utah State Route 21 |
—
|
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: Utah State Route 21 | Statement: [Beaver, Utah, secondaryAccessHighway, Utah State Route 21]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryAccessHighway Context triple: [Beaver, Utah, secondaryAccessHighway, Utah State Route 21]
-
A.
primaryHighwayComponent
Indicates that one entity serves as the main or principal highway component associated with another entity.
-
B.
connectsToHighway
chosen
Indicates that one location, road, or route has a direct access point or linkage to a highway.
-
C.
secondaryTraffic
Indicates that there is an additional, indirect, or subordinate flow of traffic associated with a primary traffic stream or event.
-
D.
hasSeparateAccessRoadFor
Indicates that one entity is served by its own distinct access road that is separate from the access road used by another entity.
-
E.
hasSeparateAccessRoad
Indicates that an entity is served by its own distinct access road, separate from other routes or shared entrances.
- 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_69f01d8328c48190bc0e5f9b9b848582 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69fce7671f108190bf3ebf54339068b5 |
completed | May 7, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69fce5b5a84c81908ac1b5b9f08d48d0 |
completed | May 7, 2026, 7:19 p.m. |
Created at: April 28, 2026, 4:44 a.m.