Triple
T28170755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West 34th Street |
E715449
|
entity |
| Predicate | hasBoroughBlockSystem |
P127995
|
FINISHED |
| Object | part of Manhattan’s numbered streets system |
—
|
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: part of Manhattan’s numbered streets system | Statement: [West 34th Street, hasBoroughBlockSystem, part of Manhattan’s numbered streets system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBoroughBlockSystem Context triple: [West 34th Street, hasBoroughBlockSystem, part of Manhattan’s numbered streets system]
-
A.
hasBorough
Indicates that one entity is located within, belongs to, or is administratively part of a specific borough.
-
B.
isInBoroughBlockLotSystem
chosen
Indicates that an entity is identified or organized within a specific borough-block-lot (BBL) property numbering system.
-
C.
hasBoroughCode
Indicates that an entity is associated with a specific borough identified by a particular code.
-
D.
hasBoroughEndpoint
Indicates that something has an endpoint located within a specific borough.
-
E.
hasBoroughCommunityDistrictCode
Indicates that a borough is associated with a specific community district code that identifies one of its administrative subdivisions.
- 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_69efd6b340f0819095680e15dcdc1830 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f7516d5b4081908588a6feb541f355 |
completed | May 3, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69f74d40ebb081909daf60623e38f41d |
completed | May 3, 2026, 1:27 p.m. |
Created at: April 27, 2026, 10:12 p.m.