Triple
T29372123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Splatterhouse |
E744880
|
entity |
| Predicate | ageRatingConcern |
P163605
|
FINISHED |
| Object | violence and gore |
—
|
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: violence and gore | Statement: [Splatterhouse, ageRatingConcern, violence and gore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ageRatingConcern Context triple: [Splatterhouse, ageRatingConcern, violence and gore]
-
A.
ageRatingControversy
chosen
Indicates that there is a dispute, concern, or notable issue regarding the appropriateness or assignment of an age rating for something.
-
B.
ageRatingContext
Indicates the contextual basis or circumstances (such as region, system, or criteria) under which an age rating is assigned or interpreted.
-
C.
ratedFor
Indicates that an entity has been evaluated and assigned a suitability or quality level for a particular purpose, context, or audience.
-
D.
ageRatingSystem
Indicates the classification scheme or standard used to assign age-appropriateness ratings to content.
-
E.
parentalRating
Indicates the content advisory classification assigned to a work, specifying the recommended minimum audience age or parental guidance level.
- 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_69f0a79ba954819094597628112c6091 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f669ab36008190bc2e3c5dbdd2050d |
completed | May 2, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69f660f4f7a88190b93c60d76b86c912 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 2:28 p.m.