Triple
T19186894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iditarod Trail Sled Dog Race finish |
E469723
|
entity |
| Predicate | startPointOfRace |
P389
|
FINISHED |
| Object | Anchorage ceremonial start |
—
|
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: Anchorage ceremonial start | Statement: [Iditarod Trail Sled Dog Race finish, startPointOfRace, Anchorage ceremonial start]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startPointOfRace Context triple: [Iditarod Trail Sled Dog Race finish, startPointOfRace, Anchorage ceremonial start]
-
A.
startedRacing
Indicates that an entity began participating in a racing activity or competition, marking the initiation of its involvement in racing.
-
B.
startPoint
chosen
Indicates the initial location or position from which an object, path, or action begins.
-
C.
raceRecordStarts
Indicates that a race record begins or is initiated at a specific point or event in time.
-
D.
raceStartType
Indicates the manner or format in which a race is initiated (e.g., type or method of starting the race).
-
E.
raceAdded
Indicates that a race event or race-related record has been newly created or incorporated into a system or dataset.
- 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_69d8dd0ad9088190a173b32657ae2e7a |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5f620f1f08190a0daaf0d1483d724 |
completed | April 20, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69e4b9bb158481909478ca2e06f3ba39 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:07 p.m.