Triple
T16720623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tipperary GAA |
E406337
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Gaelic Athletic Association county board |
C33846
|
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: Gaelic Athletic Association county board Context triple: [Tipperary GAA, instanceOf, Gaelic Athletic Association county board]
-
A.
Gaelic games county board
chosen
A Gaelic games county board is the local governing body responsible for organizing, promoting, and regulating Gaelic Athletic Association activities and competitions within a specific county.
-
B.
provincial council of the Gaelic Athletic Association
A provincial council of the Gaelic Athletic Association is a regional governing body responsible for organizing, promoting, and regulating Gaelic games and related activities within one of Ireland’s four provinces.
-
C.
Gaelic Athletic Association club
A Gaelic Athletic Association club is a community-based sports organization in Ireland (and worldwide) that promotes and fields teams in traditional Irish games such as Gaelic football, hurling, camogie, and handball under the governance of the GAA.
-
D.
Gaelic football manager
A Gaelic football manager is the individual responsible for overseeing the training, tactics, team selection, and overall performance of a Gaelic football team.
-
E.
county team organisation
A county team organisation is a structured entity responsible for managing, supporting, and coordinating a county-level sports team’s operations, administration, and competitive activities.
- 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_69d8838f242881908abd8bc138795886 |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:20 a.m.