Triple
T6851056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Final parade |
E158014
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | AFL event |
C21688
|
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: AFL event Context triple: [Grand Final parade, instanceOf, AFL event]
-
A.
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.
-
B.
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.
-
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.
American football scouting event
An American football scouting event is a structured evaluation gathering where players demonstrate their physical, technical, and mental abilities in front of coaches, scouts, and team executives to assess their potential for recruitment or draft selection.
-
E.
National Football League history event
A National Football League history event is a significant occurrence or milestone—such as a game, rule change, record, or organizational decision—that has contributed to shaping the evolution and legacy of the NFL over time.
- 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_69c6882fae988190864cbba788c5ebb4 |
completed | March 27, 2026, 1:37 p.m. |
Created at: March 27, 2026, 2:20 p.m.