Triple
T13964813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bronx Community District 7 |
E335894
|
entity |
| Predicate | hasLocalPlanningFunction |
P46513
|
FINISHED |
| Object | land use review |
—
|
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: land use review | Statement: [Bronx Community District 7, hasLocalPlanningFunction, land use review]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocalPlanningFunction Context triple: [Bronx Community District 7, hasLocalPlanningFunction, land use review]
-
A.
hasPlanningFunction
chosen
Indicates that an entity is responsible for or involved in planning, organizing, or determining future actions or strategies.
-
B.
hasPlanner
Indicates that an entity is associated with or assigned a planner responsible for organizing or managing its activities or processes.
-
C.
hasFutureMissionPlanned
Indicates that an entity has a mission or task scheduled to occur at a future time.
-
D.
hasPlanningCharacteristic
Indicates that an entity possesses a specific feature, quality, or attribute related to planning activities or processes.
-
E.
hasNearbyFunction
Indicates that one entity has another entity located close by that serves a related or supportive function.
- 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_69d81c61f3508190aaf2ca0dc0002c59 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2e7e24f08190ba939a8044860033 |
completed | April 14, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69dd465a21408190b912a42c50ffa0d9 |
completed | April 13, 2026, 7:39 p.m. |
Created at: April 9, 2026, 10:18 p.m.