Triple
T35178989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2021 Africa Cup of Nations |
E1015793
|
entity |
| Predicate | rescheduledToYear |
P119673
|
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: [2021 Africa Cup of Nations, rescheduledToYear, 2022]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rescheduledToYear Context triple: [2021 Africa Cup of Nations, rescheduledToYear, 2022]
-
A.
rescheduledTo
chosen
Indicates that an event or action has been moved from its original time to a new specified time.
-
B.
postponedToYear
Indicates that an event or action has been delayed and rescheduled to occur in the specified calendar year.
-
C.
originallyScheduledYear
Indicates the year in which something was first planned or scheduled to occur, before any later changes or rescheduling.
-
D.
rescheduled
Indicates that a previously planned event or action has been assigned a new time or date, replacing the original schedule.
-
E.
reassignmentYear
Indicates the year in which something was reassigned from one status, owner, role, or category to another.
- 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_69f76ddcc108819097f96853b7ed9ef4 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78d78d7c8819081e37e0881eafd91 |
completed | May 3, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69f78b9106008190930b3b3675b737d6 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:02 p.m.