Triple
T31547429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philadelphia City Planning Commission |
E804906
|
entity |
| Predicate | appliesPlanningCode |
P48085
|
FINISHED |
| Object | Philadelphia Zoning Code |
—
|
NE NERFINISHED |
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: Philadelphia Zoning Code | Statement: [Philadelphia City Planning Commission, appliesPlanningCode, Philadelphia Zoning Code]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesPlanningCode Context triple: [Philadelphia City Planning Commission, appliesPlanningCode, Philadelphia Zoning Code]
-
A.
planningCode
Indicates that an entity is associated with a specific planning classification or code used to govern or describe how it should be planned or managed.
-
B.
appliesCode
chosen
Indicates that one entity enforces, executes, or puts into effect a specific code, rule set, or coding scheme on another entity or context.
-
C.
hasPlanningAssociation
Indicates a relationship where one entity is involved with, linked to, or considered in the planning or preparation activities of another entity.
-
D.
plannedUnder
Indicates that one entity has been scheduled, organized, or arranged to occur within the scope, authority, or framework of another entity.
-
E.
hasPlanningType
Indicates that an entity is associated with a specific category or type used for planning or scheduling purposes.
- 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_69fe5d58c3e48190910aa3c23485e2c4 |
completed | May 8, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69fe5c92090c8190bcfa412c0a3619df |
completed | May 8, 2026, 9:58 p.m. |
Created at: April 30, 2026, 10:09 p.m.