Triple
T16846493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Booktrust Teenage Prize |
E409551
|
entity |
| Predicate | hasAgeGroupFocus |
P29430
|
FINISHED |
| Object | 13–19 |
—
|
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: 13–19 | Statement: [Booktrust Teenage Prize, hasAgeGroupFocus, 13–19]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAgeGroupFocus Context triple: [Booktrust Teenage Prize, hasAgeGroupFocus, 13–19]
-
A.
hasAgeFocus
chosen
Indicates a relationship where something is characterized or distinguished by a particular age group or age-related emphasis.
-
B.
hasApproximateAgeRange
Indicates that one entity is associated with another entity representing an estimated or non-exact span of ages.
-
C.
containsAge
Indicates that one entity includes or specifies the age value or age-related information of another entity.
-
D.
hasAge
Indicates that an entity possesses a specific age value, typically expressed as a number of time units since its birth or creation.
-
E.
hasFocusGroup
Indicates that an entity is associated with or participates in a specific focus group for targeted discussion, feedback, or research.
- 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_69d883952b048190887740a980b712ed |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b354eaf081908fe6f84a330d7866 |
completed | April 18, 2026, 4:37 p.m. |
| PD | Predicate disambiguation | batch_69e32b87b4248190aaddb05e88452356 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:24 a.m.