Triple
T15447970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kurt Gidley |
E370072
|
entity |
| Predicate | nationalTeamDebutForAustralia |
P68158
|
FINISHED |
| Object | 2007 |
—
|
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: 2007 | Statement: [Kurt Gidley, nationalTeamDebutForAustralia, 2007]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nationalTeamDebutForAustralia Context triple: [Kurt Gidley, nationalTeamDebutForAustralia, 2007]
-
A.
nationalTeamDebutCountry
Indicates the country for which an individual first made an official appearance on a national team.
-
B.
AllAustralianTeam
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.
-
C.
internationalTeamDebutYear
chosen
Indicates the year in which an entity (typically an athlete) first appeared in competition for an international team.
-
D.
nationalTeamCoachingDebutYear
Indicates the year in which a coach first officially began coaching a national team.
-
E.
openingBatsmanAustralia
Indicates that the subject is an opening batsman for the Australian cricket team.
- 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_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. |
Created at: April 10, 2026, 3:21 a.m.