Triple
T24745266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stampede Tunnel |
E618677
|
entity |
| Predicate | railroadCompletedVia |
P158103
|
FINISHED |
| Object | Northern Pacific transcontinental route |
—
|
NE NERFINISHED |
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: Northern Pacific transcontinental route | Statement: [Stampede Tunnel, railroadCompletedVia, Northern Pacific transcontinental route]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railroadCompletedVia Context triple: [Stampede Tunnel, railroadCompletedVia, Northern Pacific transcontinental route]
-
A.
railroad
Indicates that one entity constructs, operates, or provides railroad or train transportation services for another entity or area.
-
B.
railroadMet
Indicates that two or more railroads encountered or connected with each other at a specific place or time.
-
C.
railroadSuccessor
Indicates that one railroad entity directly follows or replaces another in an operational or historical succession.
-
D.
servedByRailroad
Indicates that a location or facility is provided with transportation or service by a railroad line or company.
-
E.
hasRail
Indicates that something is equipped with, includes, or is connected to a rail or rail system.
- 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_69e2fab8f95c81908bb9e552cf3280c2 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f464b4c9b0819085daa00c7c3b8b76 |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f45cf017a88190b4985b11159c907d |
completed | May 1, 2026, 7:57 a.m. |
| PDg | Predicate description generation | batch_69f464ae42e88190b3549fdf4e0b425e |
completed | May 1, 2026, 8:30 a.m. |
Created at: April 18, 2026, 4:21 a.m.