Triple
T8018229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brooklyn Community District 6 |
E186673
|
entity |
| Predicate | hasCommunityDistrictNumber |
P13282
|
FINISHED |
| Object | 6 |
—
|
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: 6 | Statement: [Brooklyn Community District 6, hasCommunityDistrictNumber, 6]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommunityDistrictNumber Context triple: [Brooklyn Community District 6, hasCommunityDistrictNumber, 6]
-
A.
communityDistrictNumber
chosen
Indicates the specific community district identifier associated with an entity or location.
-
B.
hasCommunityArea
Indicates that an entity is associated with, located in, or belongs to a particular community area.
-
C.
hasMunicipalDistrictNumber
Indicates that a municipality or local administrative unit is assigned a specific district number within its municipal structure.
-
D.
communityAreaNumber
Indicates the specific numbered community area to which an entity is assigned or associated.
-
E.
containsDistrictMunicipality
Indicates that an administrative region includes one or more district municipalities within its boundaries.
- 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_69ca82ac7fc081909b1398cf025423af |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3df626e8819098a9f8908dfdad3b |
completed | March 31, 2026, 3:22 a.m. |
| PD | Predicate disambiguation | batch_69cb048c9f488190b4fb8917a9c21bc5 |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:20 p.m.