Triple
T36035483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kerins O’Rahilly’s GAA club |
E1042383
|
entity |
| Predicate | countyCompetition |
P136800
|
FINISHED |
| Object | Kerry GAA |
E504010
|
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: Kerry GAA | Statement: [Kerins O’Rahilly’s GAA club, countyCompetition, Kerry GAA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countyCompetition Context triple: [Kerins O’Rahilly’s GAA club, countyCompetition, Kerry GAA]
-
A.
localCompetition
Indicates that two entities are competing with each other within the same local or geographically limited market or area.
-
B.
stateCompetition
Indicates a competitive relationship or contest occurring at the level of, or between, states.
-
C.
homeStateCompetition
Indicates a competitive event or rivalry that takes place within, or is specifically associated with, an entity’s home state.
-
D.
centralCompetition
Indicates a primary or core competitive relationship or contest that is central to the interaction between the entities.
-
E.
regionalCompetitionParticipation
chosen
Indicates that an entity takes part in a competition or contest organized at a regional level.
- 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_69f76e2d7e8c8190bac4e90734566799 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a0226c8b2f881909de3c1a5ba40fc49 |
completed | May 11, 2026, 6:58 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38d52f6790819089af1b2eefd7c6b8 |
completed | June 22, 2026, 6:24 a.m. |
| PD | Predicate disambiguation | batch_6a0225602acc8190978ab4aacc615b8d |
completed | May 11, 2026, 6:52 p.m. |
Created at: May 3, 2026, 4:07 p.m.