Triple
T14583388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 59th Street–Columbus Circle station |
E342249
|
entity |
| Predicate | positionRelativeToCentralPark |
P46521
|
FINISHED |
| Object | southwest corner |
—
|
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: southwest corner | Statement: [59th Street–Columbus Circle station, positionRelativeToCentralPark, southwest corner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionRelativeToCentralPark Context triple: [59th Street–Columbus Circle station, positionRelativeToCentralPark, southwest corner]
-
A.
relativeLocationToCentralPark
chosen
Indicates the spatial position or orientation of an entity in relation to Central Park.
-
B.
isCentralParkOf
Indicates that a location serves as the primary or central park for a specified area, city, or region.
-
C.
directionFromCityCenter
Indicates the compass direction in which one location lies relative to the city center.
-
D.
distanceFromGrandCentral
Indicates the spatial distance between a given entity and Grand Central.
-
E.
distanceFromPennStation
Indicates the physical distance between a given location and Penn Station.
- 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_69d822ddc0f081909cd8163c7de298cd |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb4209b988190ad2a7b2dead8ffed |
completed | April 14, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69de656a953481909a4645b004c40de7 |
completed | April 14, 2026, 4:03 p.m. |
Created at: April 10, 2026, 1:24 a.m.