Triple
T32893408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Route 91 |
E841399
|
entity |
| Predicate | currentSouthernTerminus |
P5249
|
FINISHED |
| Object | Brigham City, Utah |
—
|
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: Brigham City, Utah | Statement: [U.S. Route 91, currentSouthernTerminus, Brigham City, Utah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentSouthernTerminus Context triple: [U.S. Route 91, currentSouthernTerminus, Brigham City, Utah]
-
A.
hasSouthernTerminus
chosen
Indicates that one entity serves as the southern endpoint or terminus of another entity, such as a route, line, or path.
-
B.
southernTerminusVariant
Indicates a variant or alternative form of the southern endpoint or terminus of something (such as a route, line, or boundary).
-
C.
southTerminusRegion
Indicates that a given region serves as the southern endpoint or terminus of a specified route, feature, or entity.
-
D.
southernTerminusCountry
Indicates the country in which the southern endpoint or terminus of something (such as a route, line, or feature) is located.
-
E.
southTerminusType
Indicates the type or nature of the southern endpoint or terminus of something (such as a route, line, or boundary).
- 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_69f34945ae408190b72d8118c83beb77 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fee335cb08819097e3a0e09d5ebf49 |
completed | May 9, 2026, 7:33 a.m. |
| PD | Predicate disambiguation | batch_69fee2c74fd88190acfc045ab07b7f6b |
completed | May 9, 2026, 7:31 a.m. |
Created at: May 1, 2026, 1:18 a.m.