Triple
T16266574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jorge Lorenzo |
E394889
|
entity |
| Predicate | retiredFromMotoGP |
P2644
|
FINISHED |
| Object | 2019 |
—
|
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: 2019 | Statement: [Jorge Lorenzo, retiredFromMotoGP, 2019]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: retiredFromMotoGP Context triple: [Jorge Lorenzo, retiredFromMotoGP, 2019]
-
A.
retiredFromRacing
Indicates that an entity has permanently stopped participating in competitive racing activities.
-
B.
retiredFrom
chosen
Indicates that an entity has permanently stopped working for or being active in a specified organization, role, or activity.
-
C.
announcedRetirementFrom
Indicates that an entity has publicly declared its intention to retire from a particular role, position, organization, or activity.
-
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.
retiredFromSidelines
Indicates that an entity has ended its role or involvement from a previously inactive, observing, or non-participatory position in a given context.
- 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_69d87f221d8081909b0b2063e7528ba2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e245c839788190b974d1d0d2525b88 |
completed | April 17, 2026, 2:38 p.m. |
| PD | Predicate disambiguation | batch_69e219f259e88190bf49d8408c04178e |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:05 a.m.