Triple
T8015845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York, Westchester and Boston Railway |
E186611
|
entity |
| Predicate | peakRouteLength |
P78936
|
FINISHED |
| Object | approximately 21 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 21 miles | Statement: [New York, Westchester and Boston Railway, peakRouteLength, approximately 21 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peakRouteLength Context triple: [New York, Westchester and Boston Railway, peakRouteLength, approximately 21 miles]
-
A.
totalRouteLength
Indicates the overall distance or length of an entire route when all its segments are combined.
-
B.
tourLength
Indicates the total duration or distance covered by a tour or route.
-
C.
approximateRouteLength
chosen
Indicates the estimated total distance or length of a given route, rather than its exact measured value.
-
D.
touristCorridorLength
Indicates the measured length or extent of a designated tourist corridor or route.
-
E.
trailDistanceApprox
Indicates that the distance along a trail between two locations is approximately a specified value, allowing for some margin of error.
- 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_69ca82ac7fc081909b1398cf025423af |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3df37a00819088780e5461bc5b41 |
completed | March 31, 2026, 3:22 a.m. |
| PD | Predicate disambiguation | batch_69cb048c9f488190b4fb8917a9c21bc5 |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:20 p.m.