Triple
T24021860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Donald Cerrone |
E594843
|
entity |
| Predicate | retirementAnnouncementEvent |
P2787
|
FINISHED |
| Object | UFC 276 |
—
|
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: UFC 276 | Statement: [Donald Cerrone, retirementAnnouncementEvent, UFC 276]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: retirementAnnouncementEvent Context triple: [Donald Cerrone, retirementAnnouncementEvent, UFC 276]
-
A.
retiredAtEvent
Indicates that an entity ceased its professional or active role specifically at the time or in the context of a particular event.
-
B.
announcedInternationalRetirement
Indicates that an entity has formally declared they will no longer participate in international-level activities or competitions.
-
C.
announcementOccasion
chosen
Indicates the specific event, context, or circumstance on the basis of which an announcement is made.
-
D.
announcedRetirementBy
Indicates that one party has publicly declared the retirement of another party.
-
E.
announcedRetirementFrom
Indicates that an entity has publicly declared its intention to retire from a particular role, position, organization, or activity.
- 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_69e288be2c288190a3a46006945557f7 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d7667ff08190bfd14aa4eb776f21 |
completed | April 29, 2026, 10:03 a.m. |
| PD | Predicate disambiguation | batch_69f17639d23c8190bed93434e2f9230a |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 9:51 p.m.