Triple
T16720662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tipperary GAA |
E406337
|
entity |
| Predicate | notableCode |
P124371
|
FINISHED |
| Object | inter-county hurling |
—
|
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: inter-county hurling | Statement: [Tipperary GAA, notableCode, inter-county hurling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCode Context triple: [Tipperary GAA, notableCode, inter-county hurling]
-
A.
notableProgramming
Indicates that an entity is notably associated with programming, such as being recognized for significant work, skill, or contributions in the field of programming.
-
B.
notableCodec
Indicates that an entity is a codec of particular significance or prominence in some context.
-
C.
notableMethod
Indicates that a particular method, technique, or approach is especially significant, recognized, or noteworthy in relation to the associated entity.
-
D.
notableClass
Indicates that an entity belongs to a particularly important, distinguished, or otherwise noteworthy class or category within a given classification system.
-
E.
notableFork
Indicates that one entity is a significant fork or derivative version of another, typically diverging in a notable or influential way from the original.
- F. None of above. chosen
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_69d8838f242881908abd8bc138795886 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3874270748190ad7c3b3531293b60 |
completed | April 18, 2026, 1:29 p.m. |
| PD | Predicate disambiguation | batch_69e319c379f88190ac0adf812486f598 |
completed | April 18, 2026, 5:42 a.m. |
| PDg | Predicate description generation | batch_69e326b9e84881909a9166e65bd850d6 |
completed | April 18, 2026, 6:37 a.m. |
Created at: April 10, 2026, 5:20 a.m.