Triple
T8541653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kenya national football team |
E202209
|
entity |
| Predicate | playsInRegion |
P16438
|
FINISHED |
| Object | CECAFA competitions |
—
|
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: CECAFA competitions | Statement: [Kenya national football team, playsInRegion, CECAFA competitions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playsInRegion Context triple: [Kenya national football team, playsInRegion, CECAFA competitions]
-
A.
theatricalRegion
Indicates the geographic area or market where a theatrical performance, production, or release is presented or distributed.
-
B.
participantsRegion
chosen
Indicates that the related entities are associated with, originate from, or operate within a specified geographic region.
-
C.
isPlayedIn
Indicates that an instance of a game, sport, or performance takes place within or is hosted at a particular location or venue.
-
D.
playsInConfederationRegion
Indicates that an entity (typically a sports team or club) competes within the geographic region governed by a specific confederation.
-
E.
viewershipRegion
Indicates the geographic region or area in which content is viewed or for which its audience is measured.
- 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_69ca832461e88190a654c5e44e233aa8 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe6e10bc081909a7210c577b807fb |
completed | March 31, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69cbd111bf988190be98c92a607c6456 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:18 p.m.