Triple

T25807695
Position Surface form Disambiguated ID Type / Status
Subject Spokane, Portland and Seattle Railway E650016 entity
Predicate primaryRouteFollowed P147208 FINISHED
Object Columbia River 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: Columbia River | Statement: [Spokane, Portland and Seattle Railway, primaryRouteFollowed, Columbia River]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: primaryRouteFollowed
Context triple: [Spokane, Portland and Seattle Railway, primaryRouteFollowed, Columbia River]
  • A. primaryRouteOf chosen
    Indicates that one route is the main or most important pathway used for reaching or connecting to a particular destination or entity.
  • B. primaryRoute
    Indicates that one route is designated as the main or preferred path among possible alternatives between locations.
  • C. primaryRouteFrom
    Indicates that one entity serves as the main or preferred route originating from another entity.
  • D. primaryRouteThrough
    Indicates that one location or path serves as the main or most significant route passing through another location or area.
  • E. primaryRouteType
    Indicates the main category or kind of route associated with an entity, such as its primary mode, path, or routing classification.
  • 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_69e7ab35d264819095367f7e80c983ff completed April 21, 2026, 4:52 p.m.
NER Named-entity recognition batch_69fcf825ca7081909d06b0df33eb33f9 completed May 7, 2026, 8:37 p.m.
PD Predicate disambiguation batch_69fcf42160f0819096812a8bf590875e completed May 7, 2026, 8:20 p.m.
Created at: April 22, 2026, 7:05 a.m.