Triple

T37981955
Position Surface form Disambiguated ID Type / Status
Subject BC Rail (historical) E947574 entity
Predicate networkExtent P158702 FINISHED
Object extensive network across British Columbia 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: extensive network across British Columbia | Statement: [BC Rail (historical), networkExtent, extensive network across British Columbia]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: networkExtent
Context triple: [BC Rail (historical), networkExtent, extensive network across British Columbia]
  • A. networkScale chosen
    Indicates the relative size, capacity, or extent of a network in terms of its reach or resources.
  • B. networkArea
    Indicates that one entity defines, covers, or is responsible for a specific network area associated with another entity.
  • C. networkExtensible
    Indicates that a network can be expanded, upgraded, or adapted to support additional components, capacity, or functionality without fundamental redesign.
  • D. networkLength
    Indicates the total measured extent or distance covered by a network (e.g., of connections, links, or paths).
  • E. networkLengthContext
    Indicates the contextual conditions or parameters under which a network’s length is defined, measured, or interpreted.
  • 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_69f76ef8a1d08190a741bbbc5970e3b3 completed May 3, 2026, 3:51 p.m.
NER Named-entity recognition batch_69fbc995dc2481908b3bd4217f8101e7 completed May 6, 2026, 11:07 p.m.
PD Predicate disambiguation batch_69fbc8ee04f08190977b7ad70fc85896 completed May 6, 2026, 11:04 p.m.
Created at: May 3, 2026, 4:20 p.m.