Triple
T22161728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western Pacific Railroad |
E547686
|
entity |
| Predicate | completedFeatherRiverRouteYear |
P147212
|
FINISHED |
| Object | 1909 |
—
|
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: 1909 | Statement: [Western Pacific Railroad, completedFeatherRiverRouteYear, 1909]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: completedFeatherRiverRouteYear Context triple: [Western Pacific Railroad, completedFeatherRiverRouteYear, 1909]
-
A.
completedAsThroughRouteYear
Indicates that an entity was completed in a specific year specifically in its form or function as a through route.
-
B.
southMountainSegmentCompleted
Indicates that the construction or development of the south mountain segment has been fully completed.
-
C.
routeCompleted
Indicates that a specified route has been fully traversed or finished by the relevant entity or process.
-
D.
raceRoute
Indicates that one entity serves as the course or path along which a race or competitive event is conducted for another entity.
-
E.
completedTranscontinentalLine
Indicates that an entity has finished constructing or establishing a railway or transportation line that spans an entire continent.
- 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_69e11e3c4c5c81908d336165816b12e0 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12a2d8064819094d27ef9f15c6a1f |
completed | April 28, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69e71b41555881909b8e22718974d527 |
completed | April 21, 2026, 6:37 a.m. |
| PDg | Predicate description generation | batch_69e7222d208c819098b12c13e31af629 |
completed | April 21, 2026, 7:07 a.m. |
Created at: April 16, 2026, 8:34 p.m.