Triple
T36880164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thompson Springs, Utah |
E911457
|
entity |
| Predicate | isFormerRailroadTown |
P93251
|
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: [Thompson Springs, Utah, isFormerRailroadTown, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFormerRailroadTown Context triple: [Thompson Springs, Utah, isFormerRailroadTown, true]
-
A.
hasRailroadHistory
Indicates that an entity is associated with, involved in, or notable for historical events, operations, or developments related to railroads.
-
B.
foundingAsRailroadTown
chosen
Indicates that a settlement was originally established specifically to serve or develop around a railroad line or station.
-
C.
hasRailwayTown
Indicates that a location is associated with or contains a town characterized by the presence of a railway or railway facilities.
-
D.
formerRailroad
Indicates that an entity was previously a railroad but no longer functions as one.
-
E.
hasRailroadHistoryWith
Indicates a historical relationship or connection between entities involving railroads, such as shared development, operation, or significant events in railway history.
- 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_69f76e82339881909607a65c0503d941 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fd69b4b08190970609a0c2c3651a |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf7890008190a8bc355ff2d61c86 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:13 p.m.