Triple
T1523021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UP 200 Sled Dog Race |
E32271
|
entity |
| Predicate | openingEventType |
P17856
|
FINISHED |
| Object | downtown 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: downtown start | Statement: [UP 200 Sled Dog Race, openingEventType, downtown start]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingEventType Context triple: [UP 200 Sled Dog Race, openingEventType, downtown start]
-
A.
openedForEvent
Indicates that a venue or location is made accessible and operational specifically for a particular event.
-
B.
openingWorkOf
Indicates that one work serves as the first or introductory piece in relation to another work, such as the opening item in a sequence or collection.
-
C.
openStatus
Indicates whether an entity (such as a place, service, or resource) is currently open or available for use.
-
D.
opens
Indicates that one entity causes or allows another entity (such as an object, space, or resource) to become accessible or no longer closed.
-
E.
hasOpeningType
chosen
Indicates that one entity has, features, or is characterized by a particular type or kind of opening.
- 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_69a885e9b0ac819093a9806ad0efc82c |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a93d4756888190bf3872154de11539 |
completed | March 5, 2026, 8:22 a.m. |
| PD | Predicate disambiguation | batch_69a907ac7ea081908dd95bb5cc3b9847 |
completed | March 5, 2026, 4:33 a.m. |
Created at: March 4, 2026, 7:26 p.m.