Triple
T1420167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UEFA European Championship |
E30205
|
entity |
| Predicate | formatEvolution |
P2369
|
FINISHED |
| Object | expanded from 4 to 8 teams in 1980 |
—
|
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: expanded from 4 to 8 teams in 1980 | Statement: [UEFA European Championship, formatEvolution, expanded from 4 to 8 teams in 1980]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formatEvolution Context triple: [UEFA European Championship, formatEvolution, expanded from 4 to 8 teams in 1980]
-
A.
evolvedIn
Indicates that an entity originated or developed within a specified environment, context, or location over evolutionary time.
-
B.
futureEvolution
Indicates a predicted or potential future development or transformation of one entity into another.
-
C.
format
Indicates the specific arrangement, structure, or presentation style in which something is organized or expressed.
-
D.
designEvolution
chosen
Indicates how the design of an entity changes, develops, or is refined over time or across versions.
-
E.
typeSpecies
Indicates that a species is the designated type species that defines and anchors the taxonomic concept of a higher-level group (such as a genus).
- 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_69a498fb823c8190a67ce4c4837e641a |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c40764ec8190b85de6befcb20dda |
completed | March 1, 2026, 10:56 p.m. |
| PD | Predicate disambiguation | batch_69a4bf060b0081909ba00e6ac093a28b |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.