Triple

T32483903
Position Surface form Disambiguated ID Type / Status
Subject Royal Columbian Hospital E830185 entity
Predicate hasEmergencyCoverageFor P174493 FINISHED
Object Fraser Health region 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: Fraser Health region | Statement: [Royal Columbian Hospital, hasEmergencyCoverageFor, Fraser Health region]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasEmergencyCoverageFor
Context triple: [Royal Columbian Hospital, hasEmergencyCoverageFor, Fraser Health region]
  • A. hasEmergencyCare
    Indicates that an entity provides or is equipped with emergency medical care services for another entity or individuals.
  • B. hasEmergencyServiceProvider
    Indicates that an entity is associated with or served by a specific emergency service provider (such as police, fire, or medical services).
  • C. hasCoverage
    Indicates that one entity provides insurance or protection coverage for another entity or subject.
  • D. hasEmergencyServices
    Indicates that the subject provides or is equipped with emergency response services (such as police, fire, or medical assistance).
  • E. hasEmergencyTransport
    Indicates that an entity provides, is equipped with, or has access to emergency transportation services or vehicles.
  • F. None of above. chosen

Provenance (4 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_69f3491ff3b48190b50a7fa00bb05b1f completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6c398900c81909514f0eb568cf76c completed May 3, 2026, 3:40 a.m.
PD Predicate disambiguation batch_69f6bd25bed08190befcabd3a41ffadf completed May 3, 2026, 3:12 a.m.
PDg Predicate description generation batch_69f6c1b666188190ac43c3011a7df048 completed May 3, 2026, 3:32 a.m.
Created at: May 1, 2026, 12:58 a.m.