Triple

T11304047
Position Surface form Disambiguated ID Type / Status
Subject Boston Bar Canyon E267667 entity
Predicate transportCorridorThrough P86239 FINISHED
Object Fraser Canyon transportation corridor 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: Fraser Canyon transportation corridor | Statement: [Boston Bar Canyon, transportCorridorThrough, Fraser Canyon transportation corridor]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: transportCorridorThrough
Context triple: [Boston Bar Canyon, transportCorridorThrough, Fraser Canyon transportation corridor]
  • A. transportCorridor
    Indicates a route or pathway used to move people, goods, or resources between locations.
  • B. formsTransportCorridorBetween
    Indicates that something creates or constitutes a transportation link or route connecting two locations or entities.
  • C. partOfTransportCorridorTo
    Indicates that one entity forms a component or segment of a larger transport corridor leading to another entity.
  • D. locatedInTransportCorridor chosen
    Indicates that an entity is situated within a designated transport corridor used for the movement of people or goods.
  • E. transportSegment
    Indicates a distinct portion of a larger journey or route during which something or someone is transported from one point to another.
  • 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_69d6aaca5c24819083db46a30d86cb34 completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7e9a5c3788190ba54eda514b97903 completed April 9, 2026, 6:02 p.m.
PD Predicate disambiguation batch_69d787aa31888190860eecaa80da5b20 completed April 9, 2026, 11:04 a.m.
Created at: April 8, 2026, 9:32 p.m.