Triple

T35965643
Position Surface form Disambiguated ID Type / Status
Subject Tayside Fire and Rescue E1040134 entity
Predicate numberOfRegionalFireServicesMergedIntoSuccessor P207115 FINISHED
Object 8 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: 8 | Statement: [Tayside Fire and Rescue, numberOfRegionalFireServicesMergedIntoSuccessor, 8]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: numberOfRegionalFireServicesMergedIntoSuccessor
Context triple: [Tayside Fire and Rescue, numberOfRegionalFireServicesMergedIntoSuccessor, 8]
  • A. hasFireServicesFrom
    Indicates that one entity receives fire protection or firefighting services from another entity.
  • B. numberOfFirefightersInvolved
    Indicates the total count of firefighters who participated in or were involved in a specific event, incident, or operation.
  • C. hasFireRescueService
    Indicates that an entity is served by, or responsible for providing, a fire and rescue service.
  • D. disbandedOrAmalgamatedIn
    Indicates that an entity ceased to exist in its original form on a given date, either by being formally disbanded or by being merged into another entity.
  • E. numberOfFires
    Indicates the count of distinct fire incidents associated with or occurring in relation to an entity.
  • 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_69f76e26b21081909fd9ffb3aff6c77a completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_6a037c92f03c8190ae2751270b195423 completed May 12, 2026, 7:16 p.m.
PD Predicate disambiguation batch_6a037a0895b48190acdd88dc10db7be7 completed May 12, 2026, 7:05 p.m.
PDg Predicate description generation batch_6a037c82179081908325a59b8539b3a8 completed May 12, 2026, 7:16 p.m.
Created at: May 3, 2026, 4:07 p.m.