Triple
T6963019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AFL Women's |
E161419
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | women's Australian rules football league |
C13679
|
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: women's Australian rules football league Context triple: [AFL Women's, instanceOf, women's Australian rules football league]
-
A.
Australian rules football league
chosen
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 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.
-
C.
VFL/AFL club
A VFL/AFL club is a professional Australian rules football organization that competes in the Victorian Football League or Australian Football League, encompassing players, coaches, staff, and supporters under a shared identity.
-
D.
women's football team
A women's football team is an organized group of female players who train and compete together in the sport of football under a shared identity, such as a club, school, or national side.
-
E.
rugby league competition
A rugby league competition is an organized series of rugby league matches, typically involving multiple teams competing over a defined period to determine rankings, champions, or progression in a league or tournament structure.
- F. None of above.
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_69c68853cff881908439d488924a8283 |
completed | March 27, 2026, 1:38 p.m. |
Created at: March 27, 2026, 2:30 p.m.