Triple

T19360980
Position Surface form Disambiguated ID Type / Status
Subject Preservation District for Groups of Traditional Buildings E484277 entity
Predicate includesProtectionOf P1040 FINISHED
Object building exteriors 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: building exteriors | Statement: [Preservation District for Groups of Traditional Buildings, includesProtectionOf, building exteriors]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: includesProtectionOf
Context triple: [Preservation District for Groups of Traditional Buildings, includesProtectionOf, building exteriors]
  • A. providesProtectionIn
    Indicates that one entity offers protection or safeguarding to another entity within a specified context, location, or situation.
  • B. providesProtectionAgainst
    Indicates that one entity serves to guard, shield, or defend another entity from a specified harm, threat, or adverse effect.
  • C. protectedBy
    Indicates that one entity provides protection, defense, or safeguarding for another entity.
  • D. protects chosen
    Indicates taking action to keep someone or something safe from harm, danger, or negative effects.
  • E. hasProtectionPurpose
    Indicates that something is intended or designed to serve a protective function or goal.
  • 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_69d8e8d305088190ad13571532aa454c completed April 10, 2026, 12:10 p.m.
NER Named-entity recognition batch_69e6190c2a8081908f48dfa738248ec8 completed April 20, 2026, 12:16 p.m.
PD Predicate disambiguation batch_69e4fd54f8e48190956e73dd8969164a completed April 19, 2026, 4:05 p.m.
Created at: April 10, 2026, 1:34 p.m.