Triple
T3942776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2026 Winter Olympics |
E92073
|
entity |
| Predicate | willIncludeSport |
P15165
|
FINISHED |
| Object | alpine skiing |
—
|
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: alpine skiing | Statement: [2026 Winter Olympics, willIncludeSport, alpine skiing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: willIncludeSport Context triple: [2026 Winter Olympics, willIncludeSport, alpine skiing]
-
A.
includesSport
chosen
Indicates that one entity contains, offers, or features a particular sport as part of its activities, content, or composition.
-
B.
appliesToSports
Indicates that something is relevant, appropriate, or specifically intended for use in the context of sports.
-
C.
representsInSport
Indicates that one entity serves as an official representative of another entity within the context of a particular sport or sporting domain.
-
D.
includesCompetition
Indicates that one entity contains, features, or encompasses a competition as part of its scope or content.
-
E.
hasRelativeInSport
Indicates that one entity has a family member who participates or is involved in a sport-related activity or profession.
- 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_69aed965502c8190904ebad1203a4ae8 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef1515c688190a38332aedeed8a76 |
completed | March 9, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69aee764235081909309b3c982f322a9 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:24 p.m.