Triple
T29234828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CECAFA Cup |
E741164
|
entity |
| Predicate | hasThirdPlacePlayoff |
P66778
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [CECAFA Cup, hasThirdPlacePlayoff, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasThirdPlacePlayoff Context triple: [CECAFA Cup, hasThirdPlacePlayoff, yes]
-
A.
thirdPlacePlayoff
Indicates a match or contest held to determine which participant finishes in third place, typically between the losers of the semifinals.
-
B.
hasThirdPlaceMatch
chosen
Indicates that a competition or tournament includes a specific match played to determine the third-place finisher between the losing semifinalists or equivalent contenders.
-
C.
thirdPlacePlayOffVenue
Indicates the venue where the third-place playoff match of a competition is held.
-
D.
hasPlayoffsWith
Indicates that two entities participate together in the same playoff series, bracket, or postseason competition.
-
E.
hasThirdRound
Indicates that an entity includes, participates in, or is associated with a third round within a multi-round process or sequence.
- 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_69f0911dd6fc819097d1abb287016489 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 28, 2026, 12:28 p.m.