Triple
T16521387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peter Matera |
E401325
|
entity |
| Predicate | AllAustralianSelection |
P74666
|
FINISHED |
| Object | 1991 |
—
|
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: 1991 | Statement: [Peter Matera, AllAustralianSelection, 1991]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: AllAustralianSelection Context triple: [Peter Matera, AllAustralianSelection, 1991]
-
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.
AustraliaOvers
Indicates a relationship where one entity surpasses, exceeds, or goes beyond another in the specific context associated with Australia.
-
C.
AustraliaScore
Indicates that a scoring event or point total is attributed to Australia in a given context.
-
D.
AustralianFootballHallOfFameStatus
Indicates that an entity has a particular induction or membership status in the Australian Football Hall of Fame.
-
E.
AFLDraftPick
Indicates a selection relationship where an Australian Football League (AFL) club chooses a player with a specific draft pick in an AFL draft.
- 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_69d883838abc8190bc79cb2d41733ce2 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e804e388190b684bde2c82ab770 |
completed | April 18, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69e296995d388190b88ebe189dce890d |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:14 a.m.