Triple

T18120681
Position Surface form Disambiguated ID Type / Status
Subject Auxiliary Fire Service E433721 entity
Predicate restoredAlongside P130524 FINISHED
Object local authority fire brigades 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: local authority fire brigades | Statement: [Auxiliary Fire Service, restoredAlongside, local authority fire brigades]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: restoredAlongside
Context triple: [Auxiliary Fire Service, restoredAlongside, local authority fire brigades]
  • A. laterRestored
    Indicates that something previously altered, damaged, or removed was subsequently brought back to its earlier state or condition.
  • B. restoredBy
    Indicates that an entity has been returned to a previous or improved state through the actions or intervention of another entity.
  • C. restored
    Indicates that an entity has returned another entity to a previous or improved state, condition, or position after damage, loss, or alteration.
  • D. restoredRight
    Indicates that a previously lost, removed, or suspended right has been returned to its holder.
  • E. restoredInPart
    Indicates that something has been brought back to a previous or improved state, but only partially rather than fully.
  • 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_69d8b909e8cc81908df4cc2b8ea6d11f completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4ddd9b21c81908d23b8d9840410df completed April 19, 2026, 1:51 p.m.
PD Predicate disambiguation batch_69e43313ca788190baa224269e71de49 completed April 19, 2026, 1:42 a.m.
PDg Predicate description generation batch_69e438f5ae2c8190b11dee46534fa5a9 completed April 19, 2026, 2:07 a.m.
Created at: April 10, 2026, 10:28 a.m.