Triple
T21452173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hartsdale, New York |
E529237
|
entity |
| Predicate | commuterRailDistanceToGrandCentral |
P38946
|
FINISHED |
| Object | approximately 22 miles |
—
|
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: approximately 22 miles | Statement: [Hartsdale, New York, commuterRailDistanceToGrandCentral, approximately 22 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commuterRailDistanceToGrandCentral Context triple: [Hartsdale, New York, commuterRailDistanceToGrandCentral, approximately 22 miles]
-
A.
distanceFromGrandCentral
chosen
Indicates the spatial distance between a given entity and Grand Central.
-
B.
distanceFromPennStation
Indicates the physical distance between a given location and Penn Station.
-
C.
commuterRailTravelTimeToManhattan
Indicates the travel time by commuter rail required to reach Manhattan from a given location.
-
D.
distance to Midtown Manhattan (miles)
Indicates the physical separation between a location and Midtown Manhattan, measured in miles.
-
E.
distanceFromHobokenTerminal
Indicates the measured distance between a given location and Hoboken Terminal.
- 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_69e0c457579481909db68053ed99750c |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9e9d426d88190ae87ae9fac9c30a0 |
completed | April 23, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_69e631df1b38819088d3604854e697b4 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:07 p.m.