Triple
T11022582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | McGrath, Alaska |
E260525
|
entity |
| Predicate | hasEventRole |
P4073
|
FINISHED |
| Object | Iditarod race checkpoint |
—
|
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: Iditarod race checkpoint | Statement: [McGrath, Alaska, hasEventRole, Iditarod race checkpoint]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEventRole Context triple: [McGrath, Alaska, hasEventRole, Iditarod race checkpoint]
-
A.
eventRole
chosen
Indicates the specific function, capacity, or part an entity plays within an event or occurrence.
-
B.
hasAuthorRoleInEventsDescribed
Indicates that an entity serves as an author specifically in relation to the events described in a given work or context.
-
C.
hasStageRole
Indicates that an entity performs or holds a specific role or character in a staged performance or theatrical production.
-
D.
hasNotableRoleIn
Indicates that an entity holds a significant or noteworthy role or function within another entity, event, work, or context.
-
E.
isLinkedToEvent
Indicates that an entity has an association or connection with a specific event.
- 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_69d6aa9687448190b28d353b1b6a610e |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d797bd88188190a644adc9283cabb8 |
completed | April 9, 2026, 12:12 p.m. |
| PD | Predicate disambiguation | batch_69d72e995e008190bbffb314129ed0cd |
completed | April 9, 2026, 4:44 a.m. |
Created at: April 8, 2026, 9:25 p.m.