Triple
T15605862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2011 FIBA Africa Championship |
E375157
|
entity |
| Predicate | hostSelectionType |
P46356
|
FINISHED |
| Object | continental bid process |
—
|
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: continental bid process | Statement: [2011 FIBA Africa Championship, hostSelectionType, continental bid process]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostSelectionType Context triple: [2011 FIBA Africa Championship, hostSelectionType, continental bid process]
-
A.
hostSelection
Indicates the choice or designation of a particular host from a set of possible hosts for a given purpose or interaction.
-
B.
hostSelectionBody
Indicates the body or organization responsible for selecting or appointing the host of an event, activity, or function.
-
C.
typicalHostSelection
Indicates the usual or preferred choice of host entity that is selected in a given context or process.
-
D.
holderSelection
Indicates that a particular entity has been chosen or designated to serve as the holder of another entity or resource.
-
E.
hostCountrySelectionMethod
chosen
Indicates the process or criteria by which a host country is chosen for an event, program, or activity.
- 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_69d85ccf2794819096cda4cbcb02d478 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e7d9328819090e93d55881269a5 |
completed | April 16, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69deda844af081909e658ebc9d9b403d |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:12 a.m.