Triple
T15382549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | E for Everyone |
E367838
|
entity |
| Predicate | ageRecommendationNote |
P102642
|
FINISHED |
| Object | generally suitable for all ages |
—
|
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: generally suitable for all ages | Statement: [E for Everyone, ageRecommendationNote, generally suitable for all ages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ageRecommendationNote Context triple: [E for Everyone, ageRecommendationNote, generally suitable for all ages]
-
A.
ageRatingContext
Indicates the contextual basis or circumstances (such as region, system, or criteria) under which an age rating is assigned or interpreted.
-
B.
typicalAge
Indicates the usual or characteristic age associated with an entity, event, or condition.
-
C.
hasAgeGuidelines
Indicates that there are specified age-related rules or recommendations governing how something should be accessed, used, or engaged with.
-
D.
ageLimitYears
Indicates the maximum allowed age, expressed in years, for which something is valid, permitted, or applicable.
-
E.
intendedForAgeGroup
chosen
Indicates that something is designed, suitable, or targeted for use by a specific age group.
- 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_69d85a1551a08190ba2caea7cd51c639 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e61928c81908852c355d537ed9c |
completed | April 16, 2026, 1:41 a.m. |
| PD | Predicate disambiguation | batch_69ded27742a881909cd73cc5c7d062fd |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:19 a.m.