Triple
T444809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manhattan Community Board 6 |
E10193
|
entity |
| Predicate | communityDistrictNumber |
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: [Manhattan Community Board 6, communityDistrictNumber, 6]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: communityDistrictNumber Context triple: [Manhattan Community Board 6, communityDistrictNumber, 6]
-
A.
numberOfDistricts
Indicates the total count of districts associated with a given entity or area.
-
B.
boroughNumber
Indicates the numerical identifier assigned to a specific borough within a larger administrative or municipal division.
-
C.
district
Indicates that one entity is an administrative or electoral district that geographically contains or governs another entity.
-
D.
districtBasedOn
Indicates that one district is defined, derived, or established based on the boundaries, characteristics, or structure of another entity or area.
-
E.
hasBusinessDistrict
Indicates that a place or administrative area contains or includes a designated business district within its boundaries.
- F. None of above. chosen
Provenance (4 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_69a2e8465ef481909655c681b01e2986 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2ef459800819083cd9eef3e7b5295 |
completed | Feb. 28, 2026, 1:36 p.m. |
| PD | Predicate disambiguation | batch_69a2eddfb5508190a4e06e1b260d8b2b |
completed | Feb. 28, 2026, 1:30 p.m. |
| PDg | Predicate description generation | batch_69a2eeb9e6b0819093863959a6e5730a |
completed | Feb. 28, 2026, 1:33 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.