Triple
T11891949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Graham Arnold |
E282936
|
entity |
| Predicate | isRetiredFromPlaying |
P2644
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Graham Arnold, isRetiredFromPlaying, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRetiredFromPlaying Context triple: [Graham Arnold, isRetiredFromPlaying, true]
-
A.
hasRetiredPlayersFrom
Indicates that an entity has players who previously played for it and have since retired, originating from the specified source entity (e.g., team, league, or country).
-
B.
retirementYearAsPlayer
Indicates the year in which an individual ended their career as an active player.
-
C.
retiredFrom
chosen
Indicates that an entity has permanently stopped working for or being active in a specified organization, role, or activity.
-
D.
retiredBy
Indicates that one entity has formally ended the active status, use, or service of another entity.
-
E.
retiredTo
Indicates that an entity has permanently left active service or work and taken up residence or status in a particular place or role as their retirement destination.
- 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_69d6ab2a90b08190a4e818821cc93e6d |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8d3a3f7548190adfb567f060a175a |
completed | April 10, 2026, 10:40 a.m. |
| PD | Predicate disambiguation | batch_69d8bb2fca4481909893f3428b0871ac |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:44 p.m.