Triple
T25476194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AFL Auskick |
E638439
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Australian rules football program |
C50232
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Australian rules football program Context triple: [AFL Auskick, instanceOf, Australian rules football program]
-
A.
Australian rules football league
An Australian rules football league is an organized competition in which multiple Australian rules football clubs or teams play a structured season of matches under a common set of rules and governance.
-
B.
Australian rules football rules
Australian rules football rules define the regulations governing how the game is played, including scoring, player positions, ball movement, tackling, and officiating on an oval-shaped field.
-
C.
Australian rules football match
An Australian rules football match is a competitive game between two teams of 18 players each, played on an oval field where teams score by kicking the ball between goal and behind posts using a combination of kicking, handballing, and running.
-
D.
Australian rules football championship
An Australian rules football championship is a competitive event or series of matches that determines the premier team in a given Australian rules football league or competition for a specific season or year.
-
E.
Australian rules football player
An Australian rules football player is an athlete who competes in Australian rules football, demonstrating skills in kicking, handballing, marking, and tactical play on an oval-shaped field under the sport’s specific rules.
- F. None of above. chosen
Provenance (1 batch)
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. |
Created at: April 21, 2026, 2:26 p.m.