Triple

T33002806
Position Surface form Disambiguated ID Type / Status
Subject Philadelphia historic preservation ordinance E844416 entity
Predicate mayProtect P1040 FINISHED
Object significant interior features when designated 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: significant interior features when designated | Statement: [Philadelphia historic preservation ordinance, mayProtect, significant interior features when designated]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: mayProtect
Context triple: [Philadelphia historic preservation ordinance, mayProtect, significant interior features when designated]
  • A. protects chosen
    Indicates taking action to keep someone or something safe from harm, danger, or negative effects.
  • B. protectedBy
    Indicates that one entity provides protection, defense, or safeguarding for another entity.
  • C. mayGuarantee
    Indicates that one entity has the potential or authority to provide a guarantee for another entity or outcome.
  • D. laterProtects
    Indicates that one entity provides protection for another entity at a later point in time than some referenced event or protection.
  • E. mayGrant
    Indicates that one entity has the authority or permission to confer, assign, or bestow a right, privilege, or resource to another entity.
  • 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_69f3494e59f08190b9127c693e5c7e8f completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f6d74b20a48190900dda1014cc13a8 completed May 3, 2026, 5:04 a.m.
PD Predicate disambiguation batch_69f6d26f27dc8190ae426a3e1573933e completed May 3, 2026, 4:43 a.m.
Created at: May 1, 2026, 1:23 a.m.