Triple
T10937512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leaving Certificate |
E258374
|
entity |
| Predicate | typicalStudentAge |
P78532
|
FINISHED |
| Object | 17 |
—
|
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: 17 | Statement: [Leaving Certificate, typicalStudentAge, 17]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalStudentAge Context triple: [Leaving Certificate, typicalStudentAge, 17]
-
A.
typicalStudentDemographic
Indicates the usual or most common demographic group (e.g., age, background, characteristics) that students of a given institution, program, or course belong to.
-
B.
typicalLeavingAge
Indicates the age at which entities (such as people or groups) usually or most commonly leave a given context, place, or situation.
-
C.
typicalAge
chosen
Indicates the usual or characteristic age associated with an entity, event, or condition.
-
D.
typicalStudentStatus
Indicates the usual or standard enrollment or academic standing that a student typically holds within an educational context.
-
E.
typicalEligibilityAge
Indicates the usual or standard age at which an entity qualifies for or becomes eligible for a particular status, benefit, or activity.
- 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_69d6aa8769b4819082bfe5e61b9017f0 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d770b065288190b4216beee8e8a193 |
completed | April 9, 2026, 9:26 a.m. |
| PD | Predicate disambiguation | batch_69d72e816a98819096d6c10dfb88a66a |
completed | April 9, 2026, 4:43 a.m. |
Created at: April 8, 2026, 9:23 p.m.