Triple
T33356091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Zealand Heartland Championship unions |
E854074
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | amateur rugby union competition participants |
C46348
|
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: amateur rugby union competition participants Context triple: [New Zealand Heartland Championship unions, instanceOf, amateur rugby union competition participants]
-
A.
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.
-
B.
amateur rugby league club
An amateur rugby league club is a community-based sports organization where non-professional players train, compete, and promote the game of rugby league at a local or regional level.
-
C.
rugby union
Rugby union is a full-contact team sport played between two sides of fifteen players each, aiming to score points by carrying, passing, kicking, and grounding an oval ball in the opponent’s in-goal area under a structured set of laws.
-
D.
rugby union club
A rugby union club is an organized sports entity that fields rugby union teams, manages players and coaching staff, and participates in competitive leagues and tournaments under governing body regulations.
-
E.
rugby union region
chosen
A rugby union region is a defined geographic area governed by a regional rugby union body responsible for organizing competitions, developing the sport, and representing local clubs within the broader national or international rugby 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_69f3496acbc8819099fd0305ecc42080 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:34 a.m.