Triple
T24580314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anzac Test |
E608229
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | rugby league test match |
C34926
|
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: rugby league test match Context triple: [Anzac Test, instanceOf, rugby league test match]
-
A.
representative rugby league fixture
chosen
A representative rugby league fixture is a competitive match in which selected players from clubs or regions form special teams (such as state, national, or all-star sides) to compete at a higher representative level than regular club competition.
-
B.
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.
-
C.
rugby league home fixtures context
The rugby league home fixtures context represents the environment, conditions, and associated information surrounding a team's scheduled home matches, including venue details, dates, opponents, and relevant logistical or competitive factors.
-
D.
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.
-
E.
rugby league venue
A rugby league venue is a stadium or ground specifically designed and equipped to host rugby league matches, including facilities for players, officials, and spectators.
- 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_69e2c4ce89248190ad99e18f0638dfbb |
completed | April 17, 2026, 11:39 p.m. |
Created at: April 18, 2026, 2:29 a.m.