Triple
T20220989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Killyclogher |
E495252
|
entity |
| Predicate | hasYouthActivities |
P33012
|
FINISHED |
| Object | GAA youth teams |
—
|
LITERAL 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: GAA youth teams | Statement: [Killyclogher, hasYouthActivities, GAA youth teams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasYouthActivities Context triple: [Killyclogher, hasYouthActivities, GAA youth teams]
-
A.
hasYouthProgram
Indicates that an entity offers or is associated with an organized program or set of activities specifically designed for young people.
-
B.
hasRecreationActivity
Indicates that an entity provides, includes, or is associated with a particular recreational activity.
-
C.
hasExtracurricularProgram
Indicates that an institution or organization offers one or more organized extracurricular programs or activities beyond its primary curriculum or mission.
-
D.
hasYouthTeam
chosen
Indicates that an entity has an associated youth team that serves as its junior or developmental squad.
-
E.
hasRecreationalOrganization
Indicates that an entity is associated with, or hosts, a recreational organization such as a club, team, or leisure group.
- F. None of above.
Provenance (3 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_69da626cff80819097b530718a7c98b6 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66fd610f881908fdd22b1f8bd2efc |
completed | April 20, 2026, 6:26 p.m. |
| PD | Predicate disambiguation | batch_69e55b18609481909ab28bc8750a642f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:39 p.m.