Triple
T696997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2022 Winter Olympics |
E13914
|
entity |
| Predicate | hostSelectionMethod |
P9669
|
FINISHED |
| Object | IOC members vote |
—
|
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: IOC members vote | Statement: [2022 Winter Olympics, hostSelectionMethod, IOC members vote]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostSelectionMethod Context triple: [2022 Winter Olympics, hostSelectionMethod, IOC members vote]
-
A.
hostSelection
chosen
Indicates the choice or designation of a particular host from a set of possible hosts for a given purpose or interaction.
-
B.
holderSelection
Indicates that a particular entity has been chosen or designated to serve as the holder of another entity or resource.
-
C.
hostCitySelectionLocation
Indicates the location where the selection of a host city takes place.
-
D.
connectionEstablishmentMethod
Indicates the method or mechanism by which a connection between entities is initiated or established.
-
E.
selectionMethodChangedBy
Indicates that one entity causes or is responsible for a change in the method or criteria used to make a selection.
- 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_69a493406c408190957eeec9048a8fb6 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a0c8055881909565ebde2be8fd7a |
completed | March 1, 2026, 8:25 p.m. |
| PD | Predicate disambiguation | batch_69a49d2586b081908e052cc5ba1d2685 |
completed | March 1, 2026, 8:10 p.m. |
Created at: March 1, 2026, 7:36 p.m.