Triple
T11815680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adam Goodes |
E280993
|
entity |
| Predicate | AllAustralianTeamSelection |
P74666
|
FINISHED |
| Object | 2003 |
—
|
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: 2003 | Statement: [Adam Goodes, AllAustralianTeamSelection, 2003]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: AllAustralianTeamSelection Context triple: [Adam Goodes, AllAustralianTeamSelection, 2003]
-
A.
AllAustralianTeam
chosen
Indicates that an entity has been selected for inclusion in the All-Australian Team, representing top-level recognition in Australian rules football for a given period.
-
B.
AFLTeam
Indicates that an entity is an Australian Football League (AFL) team, i.e., a professional club competing in the AFL competition.
-
C.
AustraliaOvers
Indicates a relationship where one entity surpasses, exceeds, or goes beyond another in the specific context associated with Australia.
-
D.
teamSelection
Indicates the assignment or choice of one or more individuals or entities to be part of a specific team.
-
E.
hasAFLWTeam
Indicates that an entity possesses or is associated with a team that competes in the AFLW (Australian Football League Women's) competition.
- 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_69d6ab26aae88190b2489efcb2a24234 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a658f918819092c2db05fe2ab0ce |
completed | April 10, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69d8a24e9a088190aff7932d1ff93dbf |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:42 p.m.