Triple
T28362762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brooklyn Community Board 2 |
E718406
|
entity |
| Predicate | representsBorough |
P97858
|
FINISHED |
| Object | Brooklyn |
—
|
NE NERFINISHED |
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: Brooklyn | Statement: [Brooklyn Community Board 2, representsBorough, Brooklyn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: representsBorough Context triple: [Brooklyn Community Board 2, representsBorough, Brooklyn]
-
A.
representedBorough
chosen
Indicates that one entity serves as the political or administrative representative of a specific borough.
-
B.
hasBorough
Indicates that one entity is located within, belongs to, or is administratively part of a specific borough.
-
C.
hasBoroughEndpoint
Indicates that something has an endpoint located within a specific borough.
-
D.
hasBoroughEquivalent
Indicates that one administrative area corresponds functionally or hierarchically to a borough in another jurisdiction or classification system.
-
E.
isBoroughNumber
Indicates that a specific numerical identifier corresponds to a particular borough within a larger administrative region.
- 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_69eff6ed5af48190be4e0adf298223e0 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69fbc9d1dba881908c399b8e1dc13ce2 |
completed | May 6, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
Created at: April 28, 2026, 12:53 a.m.