Triple
T36350385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Junior Cycle |
E895185
|
entity |
| Predicate | typicalEndAge |
P34384
|
FINISHED |
| Object | 15 |
—
|
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: 15 | Statement: [Junior Cycle, typicalEndAge, 15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalEndAge Context triple: [Junior Cycle, typicalEndAge, 15]
-
A.
typicalAge
Indicates the usual or characteristic age associated with an entity, event, or condition.
-
B.
typicalAgeAtCompletion
chosen
Indicates the age at which an entity (such as a program, activity, or process) is typically completed.
-
C.
typicalLeavingAge
Indicates the age at which entities (such as people or groups) usually or most commonly leave a given context, place, or situation.
-
D.
typicalEligibilityAge
Indicates the usual or standard age at which an entity qualifies for or becomes eligible for a particular status, benefit, or activity.
-
E.
typicalMaximumAge
Indicates the usual upper age limit that an entity is expected or allowed to reach under normal conditions.
- 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_69f76e4f437c8190a1af3ea2564f41f5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:09 p.m.