Triple
T14544326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indigenous All Stars vs Māori All Stars match |
E341249
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | representative rugby league fixture |
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: representative rugby league fixture Context triple: [Indigenous All Stars vs Māori All Stars match, instanceOf, representative rugby league fixture]
-
A.
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.
-
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 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.
-
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 union competition
A rugby union competition is an organized series of rugby union matches, typically involving multiple teams competing under a defined format and rules to determine a champion or ranking.
- 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_69d822db9c8481908213ceb39585f792 |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:22 a.m.