Triple
T29873059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1986 FIFA World Cup qualification |
E758644
|
entity |
| Predicate | teamsQualifiedFromCAF |
P168695
|
FINISHED |
| Object | Algeria |
—
|
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: Algeria | Statement: [1986 FIFA World Cup qualification, teamsQualifiedFromCAF, Algeria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamsQualifiedFromCAF Context triple: [1986 FIFA World Cup qualification, teamsQualifiedFromCAF, Algeria]
-
A.
qualifiedTeamAsCafChampion
Indicates that a team has secured qualification to a competition or stage specifically as the CAF (Confederation of African Football) champion.
-
B.
numberOfQualifiedTeamsFromAfrica
Indicates the count of teams from Africa that meet the specified qualification criteria.
-
C.
firstAfricaCupOfNationsQualification
Indicates the event or instance in which an entity qualified for the Africa Cup of Nations tournament for the first time.
-
D.
UEFACupQualifier
Indicates that an entity has qualified to participate in the UEFA Cup (now UEFA Europa League) competition.
-
E.
confederationCupQualifier
Indicates that an entity has qualified for participation in a Confederations Cup tournament.
- F. None of above. chosen
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_69f2245d0d7081909e37ee328542bcd7 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f676c7a4fc8190a980f9bc778a6043 |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f673c4abec8190bc2379e66f4af0a9 |
completed | May 2, 2026, 9:59 p.m. |
| PDg | Predicate description generation | batch_69f674df80b08190adb7f7531083bbb1 |
completed | May 2, 2026, 10:04 p.m. |
Created at: April 29, 2026, 5:54 p.m.