Triple
T27981499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York Avenue (NY 110 corridor nearby) |
E706635
|
entity |
| Predicate | hasRouteDesignationNearby |
P167585
|
FINISHED |
| Object | New York State Route 110 |
—
|
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: New York State Route 110 | Statement: [New York Avenue (NY 110 corridor nearby), hasRouteDesignationNearby, New York State Route 110]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRouteDesignationNearby Context triple: [New York Avenue (NY 110 corridor nearby), hasRouteDesignationNearby, New York State Route 110]
-
A.
hasDesignationNearby
Indicates that one entity has a designation (such as a label, title, or marker) located in close physical or contextual proximity to another entity.
-
B.
hasNearbyStreet
Indicates that one entity is located close to or adjacent to a street.
-
C.
routeDesignationOf
chosen
Indicates that one entity is the official route number, code, or designation assigned to another entity representing a transportation route.
-
D.
hasNearbyStreetPattern
Indicates that one location has a street layout or configuration that is spatially close to, or in the vicinity of, another location’s street pattern.
-
E.
hasLocalRoad
Indicates that there exists a local road connection or association between the related entities.
- 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_69ef96b8b8d88190bad5e4ae966bf14e |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
Created at: April 27, 2026, 7:44 p.m.