Triple
T7234315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spokane, Portland and Seattle Railway |
E155182
|
entity |
| Predicate | builtAlong |
P49363
|
FINISHED |
| Object | north bank of the Columbia River |
—
|
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: north bank of the Columbia River | Statement: [Spokane, Portland and Seattle Railway, builtAlong, north bank of the Columbia River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: builtAlong Context triple: [Spokane, Portland and Seattle Railway, builtAlong, north bank of the Columbia River]
-
A.
builtNear
Indicates that one entity was constructed at a location geographically close to another entity.
-
B.
builtAlongside
chosen
Indicates that one entity was constructed next to or in parallel with another entity, typically during the same or a closely related time period.
-
C.
builtInThe
Indicates that something was constructed or created within a specified location, structure, or context.
-
D.
builtOn
Indicates that one entity is constructed, developed, or established using another entity as its base, foundation, or underlying platform.
-
E.
placeBuilt
Indicates that a structure or facility was constructed at a specific location.
- 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_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. |
Created at: March 27, 2026, 2:55 p.m.