Triple
T25476892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James Hird |
E638456
|
entity |
| Predicate | jumperNumberRetiredBy |
P556
|
FINISHED |
| Object | Essendon Football Club |
—
|
NE NERFINISHED |
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: Essendon Football Club | Statement: [James Hird, jumperNumberRetiredBy, Essendon Football Club]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: jumperNumberRetiredBy Context triple: [James Hird, jumperNumberRetiredBy, Essendon Football Club]
-
A.
retiredNumber
Indicates that an entity (typically a team or organization) has formally withdrawn a specific number from future use, usually to honor a particular individual or achievement associated with that number.
-
B.
wearsNumberRetiredBy
Indicates that one entity wears a jersey number that has been officially retired in honor of another entity.
-
C.
hasJerseyNumberRetired
Indicates that an entity has had its jersey number officially retired, typically in recognition of its contributions or achievements.
-
D.
retiredNumberDate
Indicates the date on which an entity’s number (such as a jersey or identifier) was officially retired from further use.
-
E.
retiredNumbers
chosen
Indicates that a team has officially retired a specific player’s jersey number, taking it out of regular use in honor of that player.
- 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_69e75db9b964819096802dcf502e577e |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f772a0248190a52aef4495a5b0a3 |
completed | May 2, 2026, 1:09 p.m. |
| PD | Predicate disambiguation | batch_69f468421ba08190880eac99135e5970 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 2:26 p.m.