Triple
T28489865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Springsville |
E720931
|
entity |
| Predicate | trackNumberOnMilesAhead |
P169279
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [Springsville, trackNumberOnMilesAhead, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trackNumberOnMilesAhead Context triple: [Springsville, trackNumberOnMilesAhead, 1]
-
A.
trackLengthMiles
Indicates the length of a track measured in miles.
-
B.
trailMilepostOn
Indicates that a specific milepost is physically located on and associated with a particular trail segment or trail route.
-
C.
approximateMileMarker
Indicates an estimated or not precisely measured position along a route expressed in miles.
-
D.
trackNumberWithinLine
Indicates the position or sequence number assigned to a track within a specific line or route.
-
E.
mainTrackDistance
Indicates the distance measured along the primary or main track between two referenced points or entities.
- F. None of above. chosen
Provenance (4 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_69f01a5a47148190b0a7e111bc432e0a |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f67d691a948190afa7fb19ae7d4ac5 |
completed | May 2, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f67c9ec1708190b26ccf402ed7b106 |
completed | May 2, 2026, 10:37 p.m. |
Created at: April 28, 2026, 3 a.m.