Triple
T3630391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kicking & Screaming |
E76939
|
entity |
| Predicate | mpaaRatingReason |
P42543
|
FINISHED |
| Object | rude humor |
—
|
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: rude humor | Statement: [Kicking & Screaming, mpaaRatingReason, rude humor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mpaaRatingReason Context triple: [Kicking & Screaming, mpaaRatingReason, rude humor]
-
A.
mpaaRating
Indicates the official Motion Picture Association of America (MPAA) content rating assigned to a film or audiovisual work.
-
B.
USRating
Indicates that an entity has been assigned a rating, classification, or evaluation according to a United States–based standard or system.
-
C.
censorshipReason
chosen
Indicates the justification or cause given for why certain content is suppressed, restricted, or removed.
-
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_69ad85dc03948190b35b7189e4175bcc |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc300223881909019982ebf194f78 |
completed | March 8, 2026, 6:42 p.m. |
| PD | Predicate disambiguation | batch_69adb8410a5881909c94818d7060b2b0 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:23 p.m.