Triple
T1173763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2018 Winter Olympics |
E24970
|
entity |
| Predicate | introducedEvents |
P8259
|
FINISHED |
| Object | big air snowboarding |
—
|
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: big air snowboarding | Statement: [2018 Winter Olympics, introducedEvents, big air snowboarding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedEvents Context triple: [2018 Winter Olympics, introducedEvents, big air snowboarding]
-
A.
introducedEvent
Indicates that an entity is responsible for bringing an event into existence or initiating it for the first time.
-
B.
introduced
Indicates that one entity caused another entity to become known, presented, or brought into use for the first time to a person, group, or context.
-
C.
featuresEvent
Indicates that an entity includes, presents, or highlights a particular event as part of its content or offering.
-
D.
introducedDuring
chosen
Indicates that one entity was first brought into existence, use, or awareness within the time period, event, or context specified by the other entity.
-
E.
inspiredEvent
Indicates that one event served as the motivation, cause, or creative stimulus for another event to occur or be conceived.
- 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_69a494082a7c819095004f423f294a64 |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bd53e4b48190abb2167f8074a6bc |
completed | March 1, 2026, 10:27 p.m. |
| PD | Predicate disambiguation | batch_69a4bb5844348190b01ac6506906ba3b |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:45 p.m.