Triple
T26176201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skwentna |
E654547
|
entity |
| Predicate | raceMileMarkerRole |
P45408
|
FINISHED |
| Object | early checkpoint on Iditarod Trail Sled Dog Race |
—
|
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: early checkpoint on Iditarod Trail Sled Dog Race | Statement: [Skwentna, raceMileMarkerRole, early checkpoint on Iditarod Trail Sled Dog Race]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: raceMileMarkerRole Context triple: [Skwentna, raceMileMarkerRole, early checkpoint on Iditarod Trail Sled Dog Race]
-
A.
raceRoute
Indicates that one entity serves as the course or path along which a race or competitive event is conducted for another entity.
-
B.
approximateMileMarker
Indicates an estimated or not precisely measured position along a route expressed in miles.
-
C.
crossesAtMilepost
Indicates that one entity crosses or intersects another at a specific milepost location.
-
D.
trackRole
chosen
Indicates that an entity holds or performs a specific role within the context of a particular track or sequence of activities.
-
E.
trailMilepostOn
Indicates that a specific milepost is physically located on and associated with a particular trail segment or trail route.
- 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_69ee5b45873c81909499203612d05d07 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60c6bc408819098c4288f77d75e38 |
completed | May 2, 2026, 2:38 p.m. |
| PD | Predicate disambiguation | batch_69f5b0021da88190bdd4cf2698c23edf |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 8:37 p.m.