Triple

T31547487
Position Surface form Disambiguated ID Type / Status
Subject Philadelphia Zoning Board of Adjustment E804907 entity
Predicate decisionsAffect P14171 FINISHED
Object real estate development in Philadelphia 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: real estate development in Philadelphia | Statement: [Philadelphia Zoning Board of Adjustment, decisionsAffect, real estate development in Philadelphia]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: decisionsAffect
Context triple: [Philadelphia Zoning Board of Adjustment, decisionsAffect, real estate development in Philadelphia]
  • A. decisionsAre
    Indicates that certain choices, judgments, or resolutions possess a specified quality, status, or classification.
  • B. decisionsConcern
    Indicates that certain decisions are about, relate to, or focus on a particular subject, issue, or entity.
  • C. decisionsTakenBy
    Indicates that one or more decisions are made or taken by a specified agent or entity.
  • D. decisionEffect chosen
    Indicates that one decision leads to, influences, or determines a particular outcome or consequence.
  • E. decisionsFormalizedAs
    Indicates that informal or conceptual decisions are captured, documented, or codified into an official, structured form.
  • 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_69f348d11a048190a65eb8384a3754ac completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69f6d16f5cb881908eed141afaaa0b51 completed May 3, 2026, 4:39 a.m.
PD Predicate disambiguation batch_69f6cfe45554819089cbbd538d992132 completed May 3, 2026, 4:32 a.m.
Created at: April 30, 2026, 10:09 p.m.