Triple
T21566217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CONMEBOL–UEFA Cup of Champions |
E532167
|
entity |
| Predicate | resumption |
P44197
|
FINISHED |
| Object | 2022 |
—
|
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: 2022 | Statement: [CONMEBOL–UEFA Cup of Champions, resumption, 2022]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resumption Context triple: [CONMEBOL–UEFA Cup of Champions, resumption, 2022]
-
A.
resumedIn
chosen
Indicates that an activity, process, or state that was previously paused or interrupted has started again within or at a specified context, time, or location.
-
B.
resumesAfter
Indicates that an activity, process, or state starts again following a pause, interruption, or completion of another specified event.
-
C.
resolution
Indicates the act of formally deciding, settling, or expressing a determined stance on an issue, often through an official decision or statement.
-
D.
reassessment
Indicates that a previously made judgment, evaluation, or decision about something is being reviewed and potentially revised.
-
E.
recovery
Indicates the process or state in which an entity regains a previous condition, function, or status after loss, damage, or decline.
- 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_69e0c460db088190828c64206a450273 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eee9c912a08190952bbc9217a957d9 |
completed | April 27, 2026, 4:44 a.m. |
| PD | Predicate disambiguation | batch_69e6320c8c2c81908bf031447d66a052 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:30 p.m.