Triple

T16177906
Position Surface form Disambiguated ID Type / Status
Subject Hamilton Palace E392611 entity
Predicate demolishedBecauseOf P13074 FINISHED
Object subsidence from coal mining 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: subsidence from coal mining | Statement: [Hamilton Palace, demolishedBecauseOf, subsidence from coal mining]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: demolishedBecauseOf
Context triple: [Hamilton Palace, demolishedBecauseOf, subsidence from coal mining]
  • A. demolishedWith
    Indicates that one entity was destroyed or torn down using another specified tool, method, or agent.
  • B. demolishedOrDestroyed
    Indicates that one entity has caused another entity to be torn down, ruined, or rendered unusable, typically through deliberate demolition or destructive force.
  • C. demolishedAfter
    Indicates that one entity was demolished at a point in time later than the demolition of another entity.
  • D. demolished
    Indicates that one entity completely destroyed or razed another entity, typically a structure or object, so that it no longer exists in its previous form.
  • E. reasonForDemolition chosen
    Indicates the cause, justification, or circumstance that led to a structure or object being demolished.
  • 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_69d87f1d32208190942e4e499a80c18c completed April 10, 2026, 4:39 a.m.
NER Named-entity recognition batch_69e2205ab3108190a84fc2dfe61d5044 completed April 17, 2026, 11:58 a.m.
PD Predicate disambiguation batch_69e219d642708190ba31a90dce76a210 completed April 17, 2026, 11:30 a.m.
Created at: April 10, 2026, 5:02 a.m.