Triple
T15447964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kurt Gidley |
E370072
|
entity |
| Predicate | retirementFromNRL |
P118821
|
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: [Kurt Gidley, retirementFromNRL, 2015]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: retirementFromNRL Context triple: [Kurt Gidley, retirementFromNRL, 2015]
-
A.
retiredFromSidelines
Indicates that an entity has ended its role or involvement from a previously inactive, observing, or non-participatory position in a given context.
-
B.
retirementFromT20i
Indicates that an entity has formally retired from participating in Twenty20 International (T20I) cricket matches.
-
C.
retiredFromRacing
Indicates that an entity has permanently stopped participating in competitive racing activities.
-
D.
retiredAsPlayerFrom
Indicates that an individual ended their professional playing career while being associated with a specific team, organization, or context.
-
E.
retiredFromRAAFService
Indicates that an individual has ended or concluded their period of service in the Royal Australian Air Force.
- 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_69d85a19180081909925012fbf4e62a3 |
completed | April 10, 2026, 2:02 a.m. |
| NER | Named-entity recognition | batch_69e03ef767b4819099f2c0919a158321 |
completed | April 16, 2026, 1:44 a.m. |
| PD | Predicate disambiguation | batch_69ded28276f481908c2038bb301e57cf |
completed | April 14, 2026, 11:49 p.m. |
| PDg | Predicate description generation | batch_69ded57005608190886cd01f640dfedb |
completed | April 15, 2026, 12:01 a.m. |
Created at: April 10, 2026, 3:21 a.m.