Triple
T29977595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1966 FIFA World Cup qualification |
E761493
|
entity |
| Predicate | allocatedPlacesToUEFA |
P168312
|
FINISHED |
| Object | 10 |
—
|
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: 10 | Statement: [1966 FIFA World Cup qualification, allocatedPlacesToUEFA, 10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allocatedPlacesToUEFA Context triple: [1966 FIFA World Cup qualification, allocatedPlacesToUEFA, 10]
-
A.
organisedOutsideUEFA
Indicates that the event or competition is organized by a body that is not under the jurisdiction or authority of UEFA.
-
B.
uefaAffiliation
Indicates that an entity is officially affiliated with, recognized by, or a member of UEFA (the Union of European Football Associations).
-
C.
typicalEuropaLeagueSpots
Indicates the usual number or range of league positions that qualify a team for the UEFA Europa League in a given competition or season.
-
D.
broughtUnderUEFAControl
Indicates that an entity has been placed under the regulatory authority or administrative oversight of UEFA.
-
E.
affiliationDateToUEFA
Indicates the date on which an entity formally became affiliated with UEFA.
- 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_69f22467626081908d5afea489590e96 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f678d69dc88190b0c31a769272f6d6 |
completed | May 2, 2026, 10:21 p.m. |
| PD | Predicate disambiguation | batch_69f66ec9919881908a187bfc7c4df192 |
completed | May 2, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69f67256d064819094be04fc1bbbc635 |
completed | May 2, 2026, 9:53 p.m. |
Created at: April 29, 2026, 6:34 p.m.