Triple
T21680137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holts Summit, Missouri |
E535081
|
entity |
| Predicate | foundedAsRailStop |
P93251
|
FINISHED |
| Object | 19th century |
—
|
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: 19th century | Statement: [Holts Summit, Missouri, foundedAsRailStop, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedAsRailStop Context triple: [Holts Summit, Missouri, foundedAsRailStop, 19th century]
-
A.
foundedAsRailroadStopFor
Indicates that one place or settlement was originally established specifically to serve as a railroad stop for another location or line.
-
B.
foundingAsRailroadTown
chosen
Indicates that a settlement was originally established specifically to serve or develop around a railroad line or station.
-
C.
hasRailroadHistory
Indicates that an entity is associated with, involved in, or notable for historical events, operations, or developments related to railroads.
-
D.
hadRailwayStation
Indicates that a place or area previously possessed a railway station, which may no longer be in existence or operation.
-
E.
openedAsRailroad
Indicates that a transportation line or route was originally inaugurated and operated as a railroad.
- 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_69e0c469b6ec8190aee4cadd1527db91 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef8a12adf08190b9b450eb26a1f33c |
completed | April 27, 2026, 4:08 p.m. |
| PD | Predicate disambiguation | batch_69e6968abfdc81909cf9e0bd72db9eca |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:43 p.m.