Triple
T7548897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2026 Commonwealth Games |
E178477
|
entity |
| Predicate | originalHostSelectionMethod |
P46356
|
FINISHED |
| Object | unopposed bid |
—
|
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: unopposed bid | Statement: [2026 Commonwealth Games, originalHostSelectionMethod, unopposed bid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalHostSelectionMethod Context triple: [2026 Commonwealth Games, originalHostSelectionMethod, unopposed bid]
-
A.
hostSelection
Indicates the choice or designation of a particular host from a set of possible hosts for a given purpose or interaction.
-
B.
originalHost
Indicates that one entity is the initial or primary host on which another entity first resided, originated, or was hosted.
-
C.
typicalHostSelection
Indicates the usual or preferred choice of host entity that is selected in a given context or process.
-
D.
hostCountrySelectionMethod
chosen
Indicates the process or criteria by which a host country is chosen for an event, program, or activity.
-
E.
alternatingHost
Indicates a relationship where two or more entities take turns serving as host in a recurring or cyclical manner.
- 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_69c69f2cbe08819088f9eb0c03ef529b |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f89b9afc8190b3e61a8e2cea7ad7 |
completed | March 27, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69c6f4daad6c8190af2b8ae88d2c8cb7 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:49 p.m.