Triple
T9285522
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northwestern Pacific Railroad |
E223383
|
entity |
| Predicate | completedThroughRoute |
P51374
|
FINISHED |
| Object | 1914 |
—
|
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: 1914 | Statement: [Northwestern Pacific Railroad, completedThroughRoute, 1914]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: completedThroughRoute Context triple: [Northwestern Pacific Railroad, completedThroughRoute, 1914]
-
A.
completedAsThroughRoute
Indicates that an action or journey was carried out by following a designated through route from start to finish.
-
B.
completedAsContinuousRoute
Indicates that an activity or journey was carried out in one uninterrupted, continuous sequence without breaks or segmentation.
-
C.
routeCompleted
chosen
Indicates that a specified route has been fully traversed or finished by the relevant entity or process.
-
D.
completedIn
Indicates that an action, process, or task was fully finished within a specified time period or duration.
-
E.
completedBefore
Indicates that one event or action was fully completed prior to the start or completion of another specified event or action.
- 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_69ca8422ddf881908a3f8f876c9f53aa |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd081fe8cc8190b6c1b481c7129689 |
completed | April 1, 2026, 11:57 a.m. |
| PD | Predicate disambiguation | batch_69cc7a576ec88190bbb787eb82e2e539 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:35 p.m.