Triple
T27925640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UEFA Technical Team |
E707824
|
entity |
| Predicate | appliesToCompetitionType |
P6642
|
FINISHED |
| Object | UEFA European Championship |
—
|
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: UEFA European Championship | Statement: [UEFA Technical Team, appliesToCompetitionType, UEFA European Championship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToCompetitionType Context triple: [UEFA Technical Team, appliesToCompetitionType, UEFA European Championship]
-
A.
appliesToCompetition
chosen
Indicates that something (such as a rule, condition, or attribute) is relevant or applicable specifically to a competition.
-
B.
appliesToCompetitionFormat
Indicates that something is relevant or specifically designed for a particular competition format.
-
C.
appliesToSportType
Indicates that something is relevant or specifically associated with a particular type or category of sport.
-
D.
coversCompetitionType
Indicates that one entity includes or addresses a particular type or category of competition.
-
E.
eligibleCompetition
Indicates that an entity meets the required conditions to participate in a particular competition.
- 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_69ef96bbf2c48190a9d0e0291457aab6 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69fb6fdc7eb081908ab8475efb38c430 |
completed | May 6, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69fb5a986e588190b7a10892bd2ff44c |
completed | May 6, 2026, 3:13 p.m. |
Created at: April 27, 2026, 6:59 p.m.