Triple
T34032300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 71st Avenue |
E872688
|
entity |
| Predicate | isInBoroughCommunityDistrict |
P43690
|
FINISHED |
| Object | Queens Community District 6 |
—
|
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: Queens Community District 6 | Statement: [71st Avenue, isInBoroughCommunityDistrict, Queens Community District 6]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInBoroughCommunityDistrict Context triple: [71st Avenue, isInBoroughCommunityDistrict, Queens Community District 6]
-
A.
locatedInBoroughCommunityDistrict
chosen
Indicates that something is situated within a specific borough community district.
-
B.
hasBoroughCommunityDistrictCode
Indicates that a borough is associated with a specific community district code that identifies one of its administrative subdivisions.
-
C.
hasBoroughOrNeighborhood
Indicates that a place is located within, or associated with, a specific borough or neighborhood.
-
D.
positionInBorough
Indicates that one entity is located within or belongs to the geographic area of a specific borough.
-
E.
hasBorough
Indicates that one entity is located within, belongs to, or is administratively part of a specific borough.
- 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_69f349a2527c81909a7cd4bda94d70ad |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70b966860819089cf92927f47c5f1 |
completed | May 3, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69f70abe43e08190b2a30930d96247c1 |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:51 a.m.