Triple
T30595041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | II Olympic Winter Games |
E778759
|
entity |
| Predicate | IOCSessionSelectingHost |
P30884
|
FINISHED |
| Object | 1926 IOC Session in Lisbon |
—
|
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: 1926 IOC Session in Lisbon | Statement: [II Olympic Winter Games, IOCSessionSelectingHost, 1926 IOC Session in Lisbon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: IOCSessionSelectingHost Context triple: [II Olympic Winter Games, IOCSessionSelectingHost, 1926 IOC Session in Lisbon]
-
A.
IOCSessionThatElectedHost
chosen
Indicates the specific IOC session during which the host (e.g., of an Olympic Games or event) was formally elected or selected.
-
B.
hostSelection
Indicates the choice or designation of a particular host from a set of possible hosts for a given purpose or interaction.
-
C.
IOCSessionLocation
Indicates the place or venue where an IOC session or meeting is held.
-
D.
typicalHostSelection
Indicates the usual or preferred choice of host entity that is selected in a given context or process.
-
E.
hostSelectionBody
Indicates the body or organization responsible for selecting or appointing the host of an event, activity, or function.
- 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_69f224a1570c8190a85d3ac330479a79 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6897e61408190add6f4bd2ffa4f84 |
completed | May 2, 2026, 11:32 p.m. |
| PD | Predicate disambiguation | batch_69f67e448a9c8190b591374d98799fe3 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:24 p.m.