Triple
T20715027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kevin Sinfield |
E509146
|
entity |
| Predicate | retiredFromRugbyLeague |
P141212
|
FINISHED |
| Object | 2015 |
—
|
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: 2015 | Statement: [Kevin Sinfield, retiredFromRugbyLeague, 2015]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: retiredFromRugbyLeague Context triple: [Kevin Sinfield, retiredFromRugbyLeague, 2015]
-
A.
retirementFromNRL
Indicates that an entity has ended or formally concluded its participation or career in the NRL.
-
B.
retiredAsPlayerFrom
Indicates that an individual ended their professional playing career while being associated with a specific team, organization, or context.
-
C.
retiredFromCFL
Indicates that an individual has ended their professional playing or working career in the Canadian Football League (CFL).
-
D.
retiredFromSidelines
Indicates that an entity has ended its role or involvement from a previously inactive, observing, or non-participatory position in a given context.
-
E.
retiredFromTestCricket
Indicates that a person has formally ended their participation in Test cricket matches.
- F. None of above. chosen
Provenance (4 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_69e0b4c40ad88190b81f77695366d328 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c1d12a9481909cce3711c1c2d9f8 |
completed | April 21, 2026, 12:16 a.m. |
| PD | Predicate disambiguation | batch_69e5c044d1108190b2b5d25de23f6401 |
completed | April 20, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69e5c3caef50819093c8159fe8d6435b |
completed | April 20, 2026, 6:12 a.m. |
Created at: April 16, 2026, 12:15 p.m.