Triple
T7234293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spokane, Portland and Seattle Railway |
E155182
|
entity |
| Predicate | mainLineCompleted |
P75931
|
FINISHED |
| Object | 1908 |
—
|
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: 1908 | Statement: [Spokane, Portland and Seattle Railway, mainLineCompleted, 1908]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainLineCompleted Context triple: [Spokane, Portland and Seattle Railway, mainLineCompleted, 1908]
-
A.
mainLine
Indicates that something serves as the primary or central line, route, or sequence among a set of related lines.
-
B.
connectsToMainLineAt
Indicates that one entity is linked or joined to a primary or central line at a specific point.
-
C.
lineServed
Indicates that a particular transportation line (such as a bus, train, or metro line) provides service to or is operated at a given stop, station, or route segment.
-
D.
finalLineMeter
Indicates that the metrical pattern or structure of the final line of a text, verse, or utterance is being specified or characterized.
-
E.
frontLineReached
Indicates that an entity has arrived at or crossed into the designated front line or primary boundary of engagement.
- 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_69c688143bfc81908d4176617735e601 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6ea552a688190a00f5d0ad982f787 |
completed | March 27, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69c6e7644648819096a5e2de5d0dbe97 |
completed | March 27, 2026, 8:24 p.m. |
| PDg | Predicate description generation | batch_69c6ea539f5c81908001524149903559 |
completed | March 27, 2026, 8:36 p.m. |
Created at: March 27, 2026, 2:55 p.m.