Triple

T18394004
Position Surface form Disambiguated ID Type / Status
Subject Terrace, British Columbia E449815 entity
Predicate isRegionalHubType P50530 FINISHED
Object service hub 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: service hub | Statement: [Terrace, British Columbia, isRegionalHubType, service hub]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isRegionalHubType
Context triple: [Terrace, British Columbia, isRegionalHubType, service hub]
  • A. isRegionalServiceCentre chosen
    Indicates that an entity functions as a regional service center responsible for providing services or support to a defined geographic area.
  • B. isMajorHubInCountry
    Indicates that a location functions as a primary or central hub within a specified country, typically in terms of transport, commerce, or connectivity.
  • C. isMajorHubType
    Indicates that an entity functions as a primary or central hub within a larger network or system.
  • D. isRegional
    Indicates that something pertains to, is characteristic of, or is limited to a specific geographic region or area.
  • E. isCentralHubOf
    Indicates that one entity functions as the primary connecting or coordinating hub for activities, resources, or interactions among multiple other entities.
  • 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_69d8b9fab8a8819086a9ddc0871715e0 completed April 10, 2026, 8:51 a.m.
NER Named-entity recognition batch_69e51844c1ec81909ec215db9b29612d completed April 19, 2026, 6 p.m.
PD Predicate disambiguation batch_69e44ff1f92c8190afbb8e85d12bf2a9 completed April 19, 2026, 3:45 a.m.
Created at: April 10, 2026, 10:46 a.m.