Triple
T10771891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manhattan Community District 3 |
E254099
|
entity |
| Predicate | boroughBlockLotPrefix |
P95384
|
FINISHED |
| Object | 1003 |
—
|
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: 1003 | Statement: [Manhattan Community District 3, boroughBlockLotPrefix, 1003]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boroughBlockLotPrefix Context triple: [Manhattan Community District 3, boroughBlockLotPrefix, 1003]
-
A.
boroughNumber
Indicates the numerical identifier assigned to a specific borough within a larger administrative or municipal division.
-
B.
roadNumberPrefix
Indicates that one entity is a prefix portion of the road number or designation used by the other entity.
-
C.
boroughBoard
Indicates a governance relationship where a borough-level board oversees, coordinates, or makes decisions affecting entities within that borough.
-
D.
squareName
Indicates that an entity is identified by or associated with the name of a square (such as a public square or plaza).
-
E.
addressPrefix
Indicates that one address string serves as the starting portion or leading segment of another address.
- 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_69d6aa5f54f4819082d0bbcb6f8797e6 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d7329a281081909cdc4b971cf69207 |
completed | April 9, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69d6f31455648190b5c24690487b1b54 |
completed | April 9, 2026, 12:30 a.m. |
| PDg | Predicate description generation | batch_69d6fa334b8c819082eaf8537084c323 |
completed | April 9, 2026, 1 a.m. |
Created at: April 8, 2026, 9:16 p.m.