Triple
T32752808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | All-Ireland Minor Football Championship |
E837542
|
entity |
| Predicate | formerAgeLimit |
P99503
|
FINISHED |
| Object | under-18 |
—
|
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: under-18 | Statement: [All-Ireland Minor Football Championship, formerAgeLimit, under-18]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerAgeLimit Context triple: [All-Ireland Minor Football Championship, formerAgeLimit, under-18]
-
A.
ageLimitIntroduced
Indicates that a specific age restriction or minimum/maximum age requirement has been formally established or put into effect for something.
-
B.
ageLimitYears
chosen
Indicates the maximum allowed age, expressed in years, for which something is valid, permitted, or applicable.
-
C.
ageLimitType
Indicates the type or category of age restriction that applies to an entity or activity.
-
D.
ageLimitAppliesAt
Indicates the specific age or point in time at which an age-related restriction or limit becomes effective for an entity.
-
E.
previousAgeOfConsent
Indicates that the specified age was the legally defined age of consent in a given jurisdiction before a subsequent change or update.
- 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_69f34937f97c8190b7f84bea045df3ae |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff9361943c81909544203cbc998a69 |
completed | May 9, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69ff913138a08190b59bdc9d8d199eb3 |
completed | May 9, 2026, 7:55 p.m. |
Created at: May 1, 2026, 1:12 a.m.