Triple
T28322978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UEFA Champions League 2019–20 |
E717327
|
entity |
| Predicate | formatChangeReason |
P6009
|
FINISHED |
| Object | COVID-19 pandemic in Europe |
—
|
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: COVID-19 pandemic in Europe | Statement: [UEFA Champions League 2019–20, formatChangeReason, COVID-19 pandemic in Europe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formatChangeReason Context triple: [UEFA Champions League 2019–20, formatChangeReason, COVID-19 pandemic in Europe]
-
A.
changeReason
Indicates the reason or justification for a modification or change made to an entity or its state.
-
B.
reasonForChange
chosen
Indicates that one entity serves as the cause, justification, or motivation for a modification or change in another entity or state.
-
C.
formatMayChange
Indicates that the format or structure of something is subject to modification and may not remain consistent over time.
-
D.
nameChangeReason
Indicates the reason or justification for a change in an entity’s name.
-
E.
formatStatus
Indicates the current state or condition of a particular format, such as whether it is valid, active, or in use.
- 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_69eff6e6c3b08190ad78de6ba7f04548 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 28, 2026, 12:26 a.m.