Triple
T14402601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CMM |
E357107
|
entity |
| Predicate | complaintHandling |
P91596
|
FINISHED |
| Object | media content complaints |
—
|
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: media content complaints | Statement: [CMM, complaintHandling, media content complaints]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: complaintHandling Context triple: [CMM, complaintHandling, media content complaints]
-
A.
handlesComplaintsOn
chosen
Indicates that one entity is responsible for receiving, managing, or resolving complaints related to another entity.
-
B.
complaintsProcedure
Indicates the formal process or mechanism through which complaints are submitted, handled, and resolved.
-
C.
complainant
Indicates that an entity is the person or party who makes a complaint or brings a grievance against another entity.
-
D.
requiresForIndividualComplaints
Indicates that one party’s ability to file or pursue individual complaints is contingent upon the involvement, approval, or fulfillment of conditions by another specified entity or factor.
-
E.
handlesAppealsIn
Indicates that an entity is responsible for processing or adjudicating appeals within a specified jurisdiction, domain, or context.
- 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_69d827927c988190ad98bb0360981783 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de90860ae481908e175decda8624d5 |
completed | April 14, 2026, 7:07 p.m. |
| PD | Predicate disambiguation | batch_69de2aa024c48190805df6a9d63deb10 |
completed | April 14, 2026, 11:53 a.m. |
Created at: April 10, 2026, 1:17 a.m.