Triple
T31984896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Matthias Mayer |
E816693
|
entity |
| Predicate | announcedRetirementDuring |
P51796
|
FINISHED |
| Object | 2022–2023 World Cup season |
—
|
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–2023 World Cup season | Statement: [Matthias Mayer, announcedRetirementDuring, 2022–2023 World Cup season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: announcedRetirementDuring Context triple: [Matthias Mayer, announcedRetirementDuring, 2022–2023 World Cup season]
-
A.
announcedRetirementBy
Indicates that one party has publicly declared the retirement of another party.
-
B.
announcedRetirementFrom
chosen
Indicates that an entity has publicly declared its intention to retire from a particular role, position, organization, or activity.
-
C.
announcedRetirementPlace
Indicates that an entity publicly declared their retirement while at or in a specific place.
-
D.
retiredAtEvent
Indicates that an entity ceased its professional or active role specifically at the time or in the context of a particular event.
-
E.
retiredFrom
Indicates that an entity has permanently stopped working for or being active in a specified organization, role, 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_69f348f6a3008190bfb59ca695fd68e2 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:12 a.m.