Triple
T24323594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UEFA Champions League Final 2020 |
E613035
|
entity |
| Predicate | reasonForNoSpectators |
P46152
|
FINISHED |
| Object | COVID-19 pandemic |
—
|
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: COVID-19 pandemic | Statement: [UEFA Champions League Final 2020, reasonForNoSpectators, COVID-19 pandemic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForNoSpectators Context triple: [UEFA Champions League Final 2020, reasonForNoSpectators, COVID-19 pandemic]
-
A.
spectatorRestrictions
Indicates limitations, conditions, or rules governing who may be present as spectators and under what circumstances.
-
B.
hasSpectators
Indicates that an event, activity, or occurrence is being watched or attended by one or more spectators.
-
C.
attendanceRestrictionReason
chosen
Indicates the reason or justification for limiting, restricting, or prohibiting attendance in a given context.
-
D.
reasonForNonParticipation
Indicates the explanation or cause for why an entity did not take part in a specified activity or event.
-
E.
spectatorsFrom
Indicates that one or more spectators originate from, are associated with, or come to an event from a particular place or source.
- 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_69e2d7db6d5c819091194918157a7c1f |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f292ae127881909ef1772278181ce3 |
completed | April 29, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69f287ad30048190b3ad3613486f277f |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 1:53 a.m.