Triple
T14617958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manhattan Community District 5 |
E343136
|
entity |
| Predicate | hasCentralBusinessDistrictRole |
P79077
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Manhattan Community District 5, hasCentralBusinessDistrictRole, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCentralBusinessDistrictRole Context triple: [Manhattan Community District 5, hasCentralBusinessDistrictRole, yes]
-
A.
isDowntownCoreOf
Indicates that a location constitutes the central, most urbanized and commercially dense area of a larger city or metropolitan region.
-
B.
hasBusinessDistrict
Indicates that a place or administrative area contains or includes a designated business district within its boundaries.
-
C.
hasMajorCommercialCentre
chosen
Indicates that a place contains or hosts a primary hub of significant commercial or business activity.
-
D.
isInBusinessDistrict
Indicates that an entity is located within a designated business or commercial district area.
-
E.
hasDowntownCharacteristic
Indicates that something possesses a feature, quality, or attribute typically associated with a downtown area.
- 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_69d822dec68081908c2553145c4051dc |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb46439b88190a4affcc7ccedab6b |
completed | April 14, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69de656f9f4c81909f815b6629a9ee39 |
completed | April 14, 2026, 4:03 p.m. |
Created at: April 10, 2026, 1:25 a.m.