Triple
T34275986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leinster Senior Hurling Championship |
E879456
|
entity |
| Predicate | notableCountyTeam |
P69211
|
FINISHED |
| Object | Kilkenny |
E250779
|
NE FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Kilkenny | Statement: [Leinster Senior Hurling Championship, notableCountyTeam, Kilkenny]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCountyTeam Context triple: [Leinster Senior Hurling Championship, notableCountyTeam, Kilkenny]
-
A.
notableTeams
chosen
Indicates that there is a noteworthy association between an entity and one or more teams with which it is significantly connected or recognized.
-
B.
hasCountyTeamAffiliation
Indicates that an entity is affiliated with, represents, or is associated with a specific county-level team.
-
C.
notableCounty
Indicates that a county holds particular significance or prominence in relation to the subject.
-
D.
notableChampionTeam
Indicates that a team is notably recognized as the champion associated with a particular competition, event, or context.
-
E.
notableTeamType
Indicates that an entity is notably associated with a team of a specified type (e.g., national team, club team, or other team category).
- F. None of above.
Provenance (4 batches)
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_69f349b5f6648190b9420d94a4cd16e0 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3823a6520081908900f2b2615b1138 |
completed | June 21, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:56 a.m.