Triple
T3188074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 59th Street |
E66749
|
entity |
| Predicate | streetNumbering |
P33926
|
FINISHED |
| Object | 59 |
—
|
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: 59 | Statement: [59th Street, streetNumbering, 59]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: streetNumbering Context triple: [59th Street, streetNumbering, 59]
-
A.
isNumberedStreet
chosen
Indicates that a street is designated primarily by a number (e.g., "1st Street," "42nd Avenue") rather than by a proper name.
-
B.
hasJunctionNumbering
Indicates that a road or route is assigned a specific numbering system for its junctions or intersections.
-
C.
boroughNumber
Indicates the numerical identifier assigned to a specific borough within a larger administrative or municipal division.
-
D.
roadNumberingZone
Indicates the designated numbering zone or area within which a particular road’s identification or route number is assigned.
-
E.
routeNumberingAuthority
Indicates the authority or organization responsible for assigning and managing the official number designation of a route.
- 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_69ad8587c1bc8190a2595f2c22ee1001 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada6e279288190843837751e852c9e |
completed | March 8, 2026, 4:42 p.m. |
| PD | Predicate disambiguation | batch_69ad9e04290481909092ddfbe6fdaabc |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:06 p.m.