Triple
T13532885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Brooklyn |
E323179
|
entity |
| Predicate | governmentRegionFor |
P110728
|
FINISHED |
| Object | New York City Council districts in central Brooklyn |
—
|
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: New York City Council districts in central Brooklyn | Statement: [Central Brooklyn, governmentRegionFor, New York City Council districts in central Brooklyn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governmentRegionFor Context triple: [Central Brooklyn, governmentRegionFor, New York City Council districts in central Brooklyn]
-
A.
exportRegion
Indicates the region or geographic area from which goods, services, or resources are exported.
-
B.
countyRegion
Indicates that a county is located within, or is administratively part of, a larger geographic region.
-
C.
placeRegion
Indicates that a place is located within, or is part of, a larger geographic or administrative region.
-
D.
regionOfState
Indicates that one administrative or geographical region is a subdivision or part of a larger state.
-
E.
policyRegion
Indicates the geographic or administrative region to which a particular policy applies or is associated.
- 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_69d8076776248190bdf0d4fa1f85a5fc |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbafbb34548190a6b44faa48125cd4 |
completed | April 12, 2026, 2:44 p.m. |
| PD | Predicate disambiguation | batch_69dbae1046c48190b4ee98c6c9cb9d85 |
completed | April 12, 2026, 2:37 p.m. |
| PDg | Predicate description generation | batch_69dbaecc98cc8190829f5be759c4f1e3 |
completed | April 12, 2026, 2:40 p.m. |
Created at: April 9, 2026, 9:44 p.m.