Triple
T3942775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2026 Winter Olympics |
E92073
|
entity |
| Predicate | willIncludeEventType |
P14526
|
FINISHED |
| Object | winter sports |
—
|
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: winter sports | Statement: [2026 Winter Olympics, willIncludeEventType, winter sports]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: willIncludeEventType Context triple: [2026 Winter Olympics, willIncludeEventType, winter sports]
-
A.
hasEventType
chosen
Indicates that an event is associated with, or classified under, a specific type or category of event.
-
B.
multiEventsIncluded
Indicates that multiple distinct events are collectively contained within, or form part of, a larger event set or grouping.
-
C.
hasSubEvent
Indicates that an event is composed of, or includes as part of its structure, another event that occurs within it.
-
D.
participationIncludes
Indicates that a broader participation instance encompasses or contains a more specific participation instance as part of it.
-
E.
coversEvent
Indicates that one event includes, spans, or encompasses the time period or occurrence of another 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_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.