Triple
T4668966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paul Maurice |
E102914
|
entity |
| Predicate | reasonForEarlyRetirementAsPlayer |
P10984
|
FINISHED |
| Object | eye injury |
—
|
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: eye injury | Statement: [Paul Maurice, reasonForEarlyRetirementAsPlayer, eye injury]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForEarlyRetirementAsPlayer Context triple: [Paul Maurice, reasonForEarlyRetirementAsPlayer, eye injury]
-
A.
causeOfEarlyRetirement
chosen
Indicates that one entity is the reason or contributing factor leading another entity to retire earlier than the typical or expected time.
-
B.
retirementYearAsPlayer
Indicates the year in which an individual ended their career as an active player.
-
C.
forcedToRetire
Indicates that an entity was compelled, rather than choosing voluntarily, to end their professional role or career.
-
D.
announcedRetirementFrom
Indicates that an entity has publicly declared its intention to retire from a particular role, position, organization, or activity.
-
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_69bd43d9cba4819086c1ab1c2d9d2133 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd655aceb081908100ffc0498fe183 |
completed | March 20, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69bd6215864c8190b50ba0f63ba87d0c |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:15 p.m.