Triple
T31711663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kick-Ass 2 (comic book) |
E809335
|
entity |
| Predicate | hasViolenceRating |
P80416
|
FINISHED |
| Object | explicit |
—
|
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: explicit | Statement: [Kick-Ass 2 (comic book), hasViolenceRating, explicit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasViolenceRating Context triple: [Kick-Ass 2 (comic book), hasViolenceRating, explicit]
-
A.
containsViolence
Indicates that the subject includes, depicts, or involves acts of physical harm, aggression, or violent behavior.
-
B.
containsGraphicViolence
Indicates that the subject includes depictions of explicit, intense, or realistic physical harm or brutality.
-
C.
hasContentRating
Indicates that something is associated with a specified content rating that reflects its suitability for particular audiences.
-
D.
violenceLevel
chosen
Indicates the degree or intensity of violent behavior, actions, or content present in or associated with an entity.
-
E.
ageRatingControversy
Indicates that there is a dispute, concern, or notable issue regarding the appropriateness or assignment of an age rating for something.
- 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_69f348df4e048190a4a5a9932ada78d6 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fbbc49da8c8190902bbb05d2477cab |
completed | May 6, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69fbb13f34b08190bbbb220ac1e6e666 |
completed | May 6, 2026, 9:23 p.m. |
Created at: April 30, 2026, 11:15 p.m.