Triple
T828395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke of Edinburgh’s Award |
E17907
|
entity |
| Predicate | targetAgeGroup |
P19123
|
FINISHED |
| Object | young people aged 14 to 24 |
—
|
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: young people aged 14 to 24 | Statement: [Duke of Edinburgh’s Award, targetAgeGroup, young people aged 14 to 24]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetAgeGroup Context triple: [Duke of Edinburgh’s Award, targetAgeGroup, young people aged 14 to 24]
-
A.
ageGroup
chosen
Indicates the categorical age range or bracket to which an entity belongs.
-
B.
ageRange
Indicates the span of ages within which an entity or relationship is considered valid or applicable.
-
C.
portraysAgeGroup
Indicates that one entity depicts or represents another entity as belonging to a particular age group.
-
D.
targetStudentGroup
Indicates a relationship where something is directed, tailored, or intended specifically for a particular group of students.
-
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_69a4937c9c188190aaa216f6b466f452 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ab99b1e48190afad1f073348b29a |
completed | March 1, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_69a4aa79a6488190a634388e071ed9b7 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:38 p.m.