Triple
T24618895
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Route 128 station |
E609348
|
entity |
| Predicate | distanceFromBostonSouthStation |
P111565
|
FINISHED |
| Object | approximately 11 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 11 miles | Statement: [Route 128 station, distanceFromBostonSouthStation, approximately 11 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromBostonSouthStation Context triple: [Route 128 station, distanceFromBostonSouthStation, approximately 11 miles]
-
A.
distanceFromBoston
Indicates the spatial distance between a given entity’s location and the city of Boston.
-
B.
distanceFromSouthStation
chosen
Indicates the measured distance between a given location or entity and South Station.
-
C.
distanceFromGrandCentral
Indicates the spatial distance between a given entity and Grand Central.
-
D.
distanceFromBaltimorePennStation
Indicates the measured distance between a given location and Baltimore Penn Station.
-
E.
distanceToBostonByRoad
Indicates the road travel distance between a given location and Boston.
- 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_69e2c4d1140081909c58667bf68f80c3 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6ca751c8190a040c10d701ecf3a |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:32 a.m.