Triple
T29132654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lexington Avenue between 25th and 26th Streets |
E738420
|
entity |
| Predicate | crossStreetAtSouthernEnd |
P72012
|
FINISHED |
| Object | East 25th Street |
—
|
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: East 25th Street | Statement: [Lexington Avenue between 25th and 26th Streets, crossStreetAtSouthernEnd, East 25th Street]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crossStreetAtSouthernEnd Context triple: [Lexington Avenue between 25th and 26th Streets, crossStreetAtSouthernEnd, East 25th Street]
-
A.
crossesStreet
Indicates that an entity moves from one side of a street to the other, traversing the street’s width.
-
B.
isDowntownEndpointOf
Indicates that a location serves as the downtown terminus or endpoint of a route, line, or path.
-
C.
isSouthernmostHighwayCrossingOf
Indicates that one location is the furthest-south point at which a particular highway crosses a specified geographic feature or boundary.
-
D.
roadTerminusOf
Indicates that a road ends at, or has its terminal point at, the referenced location or route.
-
E.
hasCrossStreets
chosen
Indicates that a location is situated at or near the intersection of the specified streets.
- 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_69f07cb3adb48190a9e0e169cd026634 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d26ceb08819091c71c001e954936 |
completed | May 3, 2026, 4:43 a.m. |
Created at: April 28, 2026, 11:32 a.m.