Triple
T30669125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Livingston, Montana |
E780744
|
entity |
| Predicate | hasOldWestHeritage |
P169999
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Livingston, Montana, hasOldWestHeritage, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOldWestHeritage Context triple: [Livingston, Montana, hasOldWestHeritage, true]
-
A.
wasFrontierTownIn
Indicates that a town functioned as a frontier settlement within a specified region or territorial jurisdiction.
-
B.
historicalNameInTheWest
Indicates that an entity is known or referred to by a particular historical name specifically in Western contexts or traditions.
-
C.
historicalFrontier
Indicates a boundary or border that historically separated two regions, territories, or spheres of influence.
-
D.
isHistoricRoute66Site
Indicates that a location is situated on, or historically associated with, the original U.S. Route 66 highway and recognized as part of its historic route.
-
E.
hasRailroadHistory
Indicates that an entity is associated with, involved in, or notable for historical events, operations, or developments related to railroads.
- F. None of above. chosen
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_69f224a7fc208190a07d6d3879b31640 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68b121eac81909e90416207bc1157 |
completed | May 2, 2026, 11:38 p.m. |
| PD | Predicate disambiguation | batch_69f6861170d08190bb98be609d436f84 |
completed | May 2, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69f688034580819086a0f9100645f8ba |
completed | May 2, 2026, 11:25 p.m. |
Created at: April 29, 2026, 8:31 p.m.