Triple
T7951415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1000 Ways to Die |
E184621
|
entity |
| Predicate | hasParentalRating |
P36218
|
FINISHED |
| Object | TV-14 |
—
|
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: TV-14 | Statement: [1000 Ways to Die, hasParentalRating, TV-14]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParentalRating Context triple: [1000 Ways to Die, hasParentalRating, TV-14]
-
A.
hasContentRating
chosen
Indicates that something is associated with a specified content rating that reflects its suitability for particular audiences.
-
B.
mpaaRating
Indicates the official Motion Picture Association of America (MPAA) content rating assigned to a film or audiovisual work.
-
C.
hasAdultRank
Indicates that an entity holds a status or position classified as an adult-level rank within a given system or hierarchy.
-
D.
PEGIRating
Indicates the creditworthiness assessment assigned by the PEGI rating system, reflecting the level of financial risk associated with an entity.
-
E.
CPVRating
Indicates a content rating relationship that specifies the level of suitability or restriction of some media or material according to the CPV rating system.
- 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_69ca8292cba881908a64427b938dac47 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3b5b7450819091e4e6f21e9d832d |
completed | March 31, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69cb0473d7dc8190a25d0cf460b9fcbe |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:10 p.m.