Triple

T33099594
Position Surface form Disambiguated ID Type / Status
Subject British electricity transmission network E847005 entity
Predicate doesNotCoverTerritory P10124 FINISHED
Object Northern Ireland 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: Northern Ireland | Statement: [British electricity transmission network, doesNotCoverTerritory, Northern Ireland]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: doesNotCoverTerritory
Context triple: [British electricity transmission network, doesNotCoverTerritory, Northern Ireland]
  • A. doesNotCover chosen
    Indicates that one entity fails to include, protect, or extend over another entity or area.
  • B. doesNotGenerallyApplyTo
    Indicates that a rule, property, or condition is typically not relevant or applicable to the referenced entity or situation in most cases.
  • C. doesNotProvideFor
    Indicates that one entity fails or is not responsible for supplying support, resources, or necessary provisions to another entity.
  • D. doesNotServe
    Indicates that one entity explicitly does not provide a service, function, or role to another entity.
  • E. sometimesIncludesTerritory
    Indicates that one entity occasionally, but not consistently, encompasses or contains the territory of another entity.
  • 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_69f3495590dc8190aa04f3dec74ce976 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f6db6af1d88190989810182354d60f completed May 3, 2026, 5:21 a.m.
PD Predicate disambiguation batch_69f6d82d068c8190940a3200ed760e38 completed May 3, 2026, 5:07 a.m.
Created at: May 1, 2026, 1:26 a.m.