Triple
T32806023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PEGI |
E839021
|
entity |
| Predicate | hasAgeRatingCategory |
P110301
|
FINISHED |
| Object | PEGI 3 |
—
|
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: PEGI 3 | Statement: [PEGI, hasAgeRatingCategory, PEGI 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAgeRatingCategory Context triple: [PEGI, hasAgeRatingCategory, PEGI 3]
-
A.
hasAgeClassification
chosen
Indicates that an entity is associated with a specific age-based category or grouping.
-
B.
ageRatingContext
Indicates the contextual basis or circumstances (such as region, system, or criteria) under which an age rating is assigned or interpreted.
-
C.
hasContentRating
Indicates that something is associated with a specified content rating that reflects its suitability for particular audiences.
-
D.
ratedFor
Indicates that an entity has been evaluated and assigned a suitability or quality level for a particular purpose, context, or audience.
-
E.
ageRatingSystem
Indicates the classification scheme or standard used to assign age-appropriateness ratings to content.
- 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_69f3493d35208190b4351b4e85f2fa16 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d16f5cb881908eed141afaaa0b51 |
completed | May 3, 2026, 4:39 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe45554819089cbbd538d992132 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:15 a.m.