Triple

T11416864
Position Surface form Disambiguated ID Type / Status
Subject Category A listed building E270513 entity
Predicate requiresConsentFor P87597 FINISHED
Object demolition 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: demolition | Statement: [Category A listed building, requiresConsentFor, demolition]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: requiresConsentFor
Context triple: [Category A listed building, requiresConsentFor, demolition]
  • A. requiresConsentOfParties
    Indicates that an action or agreement can only proceed if all involved parties have explicitly given their consent.
  • B. requiresAgreementWith chosen
    Indicates that one entity’s action, decision, or validity is contingent upon obtaining consent or formal agreement from another specified entity.
  • C. requiresCautionIn
    Indicates that engaging with or operating within the referenced context, situation, or environment demands heightened care, attention, or precaution.
  • D. complianceRequiredFor
    Indicates that one entity must adhere to or satisfy the rules, standards, or conditions defined by another entity.
  • E. requiredTo
    Indicates that one entity has an obligation or necessity to perform an action or satisfy a condition in relation to another entity or context.
  • 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_69d6aaddeaa8819088b30ef7b50598c9 completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d801b0236c81908122ce3fc7b4fde7 completed April 9, 2026, 7:44 p.m.
PD Predicate disambiguation batch_69d7e70ffd708190b62a78ebcbce9f78 completed April 9, 2026, 5:51 p.m.
Created at: April 8, 2026, 9:34 p.m.