Triple
T24702644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 66th Street–Lincoln Center |
E611791
|
entity |
| Predicate | isLocalStop |
P144940
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [66th Street–Lincoln Center, isLocalStop, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLocalStop Context triple: [66th Street–Lincoln Center, isLocalStop, yes]
-
A.
isLocalStopFor
chosen
Indicates that a particular stop or station serves as a stopping point for a local (non-express) service or route.
-
B.
isPassengerStop
Indicates that a location serves as a designated place where passengers may board or alight from a vehicle or transport service.
-
C.
hasStopNear
Indicates that one entity has a stop or stopping point located in close proximity to another entity.
-
D.
isLocalStation
Indicates that a station operates primarily within a limited local area or serves as a stop on a local (rather than regional or long-distance) service.
-
E.
isLocalStationFor
Indicates that a station serves a specific local area or locality as its primary service point.
- 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_69e2c4d76d148190b58ad612467149a5 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442a977b08190b44eac040cb90211 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 3:23 a.m.