Triple
T29234782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kenya national football team |
E741163
|
entity |
| Predicate | FIFAtrigramme |
P6278
|
FINISHED |
| Object | KEN |
—
|
NE NERFINISHED |
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: KEN | Statement: [Kenya national football team, FIFAtrigramme, KEN]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: FIFAtrigramme Context triple: [Kenya national football team, FIFAtrigramme, KEN]
-
A.
FIFAcode
chosen
Indicates the standardized three-letter country or territory code assigned by FIFA to represent a national football team in international competitions.
-
B.
fifaTrigrammeStatusAfterDissolution
Indicates the status assigned to a country's FIFA trigram code after the dissolution of that country or its football association.
-
C.
fifaRecognized
Indicates that an organization, competition, or entity is officially recognized or sanctioned by FIFA as meeting its standards or falling under its authority.
-
D.
team2FIFAcode
Indicates the FIFA country code assigned to the second team involved in a match or comparison.
-
E.
FIFAentry
Indicates that an entity is officially entered or registered in a FIFA-related competition, ranking, or organizational context.
- 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_69f6646309648190806dece783dd9e55 |
completed | May 2, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f65c24f8b48190af81b575f3c15be5 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 12:28 p.m.