Triple
T32806134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USK |
E839023
|
entity |
| Predicate | contentCriteria |
P119079
|
FINISHED |
| Object | violence |
—
|
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 | Statement: [USK, contentCriteria, violence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contentCriteria Context triple: [USK, contentCriteria, violence]
-
A.
contentIs
Indicates that one entity serves as, or is equivalent to, the content contained within another entity.
-
B.
contentAccess
Indicates that one entity is permitted to retrieve, view, or otherwise use the content provided or controlled by another entity.
-
C.
contentRestriction
chosen
Indicates that access to or use of certain content is limited or controlled based on specified rules or conditions.
-
D.
contentDescriptor
Indicates that something provides a description or characterization of the content of another entity (such as a resource, item, or work).
-
E.
featuredContentType
Indicates the specific type or category of content that is highlighted or promoted as featured.
- 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_69f3493d35208190b4351b4e85f2fa16 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7764ab1fc81909f9348db87bd7692 |
completed | May 3, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f76905d9c88190b1ee810bc9ab644f |
completed | May 3, 2026, 3:25 p.m. |
Created at: May 1, 2026, 1:15 a.m.