Triple

T18665181
Position Surface form Disambiguated ID Type / Status
Subject Richmond district, Halifax E456305 entity
Predicate extentOfDamage P132202 FINISHED
Object almost completely devastated 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: almost completely devastated | Statement: [Richmond district, Halifax, extentOfDamage, almost completely devastated]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: extentOfDamage
Context triple: [Richmond district, Halifax, extentOfDamage, almost completely devastated]
  • A. damageTo
    Indicates a relationship where one entity causes harm, loss, or deterioration to another entity.
  • B. damagedIn
    Indicates that an entity has suffered harm, impairment, or destruction as a result of a specified event, process, or condition.
  • C. economicDamageApprox
    Indicates that one entity has caused or is associated with an estimated or approximate amount of economic damage to another entity or system.
  • D. economicDamageRank
    Indicates the relative severity or position of an entity in terms of the economic damage it causes or experiences compared to others.
  • E. damageAssessedBy
    Indicates that the extent or nature of damage to something has been evaluated or determined by a particular agent or authority.
  • 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_69d8d38f72b4819090a935175d9ca8af completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e5508e02788190bdea6099f08db4f0 completed April 19, 2026, 10 p.m.
PD Predicate disambiguation batch_69e478db7a248190a8c6584673773923 completed April 19, 2026, 6:40 a.m.
PDg Predicate description generation batch_69e484133ee48190a80f1889d79f34c9 completed April 19, 2026, 7:28 a.m.
Created at: April 10, 2026, 11:48 a.m.