Triple
T35136289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2000 Africa Cup of Nations |
E1014580
|
entity |
| Predicate | notableNickNameOfChampion |
P25214
|
FINISHED |
| Object | Indomitable Lions |
E321875
|
NE 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: Indomitable Lions | Statement: [2000 Africa Cup of Nations, notableNickNameOfChampion, Indomitable Lions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableNickNameOfChampion Context triple: [2000 Africa Cup of Nations, notableNickNameOfChampion, Indomitable Lions]
-
A.
notableNickname
chosen
Indicates that one entity is a well-known or widely recognized nickname or moniker for another entity.
-
B.
notableFormerChampion
Indicates that an entity was once a champion of something and is recognized as particularly distinguished or prominent in that former champion role.
-
C.
notableMultipleIndividualChampion
Indicates that an entity has achieved champion status multiple times, highlighting repeated notable victories or titles.
-
D.
notablePlayNickname
Indicates that a particular play or performance is commonly known by a specific nickname.
-
E.
notableGameNickname
Indicates that an entity is a well-known or commonly used nickname for a particular game.
- F. None of above.
Provenance (4 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_69f76dd9c1848190af70d4882a2c1ad7 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37d9570c3c8190908abc24d05ec126 |
completed | June 21, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_6a037a016960819093ed4990fb4d9d36 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:02 p.m.