Triple
T21276153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Northern Railway (U.S.) |
E524391
|
entity |
| Predicate | completedMainLineToPacific |
P73325
|
FINISHED |
| Object | 1893 |
—
|
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: 1893 | Statement: [Great Northern Railway (U.S.), completedMainLineToPacific, 1893]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: completedMainLineToPacific Context triple: [Great Northern Railway (U.S.), completedMainLineToPacific, 1893]
-
A.
completedTranscontinentalLine
chosen
Indicates that an entity has finished constructing or establishing a railway or transportation line that spans an entire continent.
-
B.
dateOfPacificArrival
Indicates the date on which an entity arrived at a location on or in the Pacific region.
-
C.
completedLineToHouston
Indicates that an entity has finished or fulfilled a line, route, or connection directed to or associated with Houston.
-
D.
completedLineToGalveston
Indicates that a line (such as a route, track, or connection) has been fully completed extending to Galveston.
-
E.
completionDateMainLine
Indicates the date on which the primary or main phase of an activity, project, or process is completed.
- 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_69e0b516293c819089458ea2ec85f85e |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e736577fd48190a0038a6ac5678668 |
completed | April 21, 2026, 8:33 a.m. |
| PD | Predicate disambiguation | batch_69e5f6161dac8190b06009cd180e3ff7 |
completed | April 20, 2026, 9:47 a.m. |
Created at: April 16, 2026, 4:02 p.m.