Triple
T4590170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Newton Hills |
E103465
|
entity |
| Predicate | approximateDistanceFromStartOnBostonMarathonCourse |
P20523
|
FINISHED |
| Object | between miles 16 and 21 |
—
|
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: between miles 16 and 21 | Statement: [Newton Hills, approximateDistanceFromStartOnBostonMarathonCourse, between miles 16 and 21]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateDistanceFromStartOnBostonMarathonCourse Context triple: [Newton Hills, approximateDistanceFromStartOnBostonMarathonCourse, between miles 16 and 21]
-
A.
approximateMileMarker
chosen
Indicates an estimated or not precisely measured position along a route expressed in miles.
-
B.
approximateDistanceFrom
Indicates an estimated or rough measure of how far one entity is from another.
-
C.
approximateRoundTripDistanceFromTrailhead
Indicates the estimated total distance of a complete out-and-back journey measured from the trailhead.
-
D.
approximateLengthInMeters
Indicates the estimated or roughly measured length of something expressed in meters.
-
E.
approximateLengthInMiles
Indicates the estimated distance or extent of something measured in miles.
- 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_69bd43dccaf08190aa89e9991a289719 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd592232888190af33c47636ca835d |
completed | March 20, 2026, 2:26 p.m. |
| PD | Predicate disambiguation | batch_69bd522acbcc8190bf24d9517793a2c1 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:11 p.m.