Triple
T15116886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AFL Showdown derbies |
E361063
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Australian Football League rivalry |
C35460
|
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 Football League rivalry Context triple: [AFL Showdown derbies, instanceOf, Australian Football League rivalry]
-
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 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.
-
C.
A-League Men rivalry
An A-League Men rivalry is a recurring, highly competitive football matchup between two A-League Men clubs characterized by historical tension, passionate fan engagement, and significant impact on league narratives and standings.
-
D.
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.
-
E.
rugby league rivalry
A rugby league rivalry is a recurring, often intense competitive relationship between two rugby league teams, fueled by historical, geographic, cultural, or competitive factors that heighten the significance of their matches.
- 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_69d85a0491ec8190830960be8fafb994 |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:05 a.m.