Triple
T29257962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Union Station (Louisville, Kentucky) |
E741755
|
entity |
| Predicate | usedAsRailTerminalUntil |
P32009
|
FINISHED |
| Object | 1970s |
—
|
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: 1970s | Statement: [Union Station (Louisville, Kentucky), usedAsRailTerminalUntil, 1970s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsRailTerminalUntil Context triple: [Union Station (Louisville, Kentucky), usedAsRailTerminalUntil, 1970s]
-
A.
foundedAsRailroadStopFor
Indicates that one place or settlement was originally established specifically to serve as a railroad stop for another location or line.
-
B.
formerRailUse
chosen
Indicates that an entity previously served a particular railway-related function or purpose, but no longer does so.
-
C.
openedAsRailTerminal
Indicates that a facility or location began operation specifically as a rail terminal when it first opened.
-
D.
usedByRailroad
Indicates that something is utilized or operated by a railroad or railway company.
-
E.
originalRailroadTerminalReplaced
Indicates that one railroad terminal has been superseded or taken the place of another as the primary terminal.
- 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_69f0912065c08190bddd23e20e8ef18e |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
Created at: April 28, 2026, 12:39 p.m.