Triple
T20255014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M (Australia) |
E498667
|
entity |
| Predicate | typicalContentDescriptors |
P139410
|
FINISHED |
| Object | moderate 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: moderate violence | Statement: [M (Australia), typicalContentDescriptors, moderate violence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalContentDescriptors Context triple: [M (Australia), typicalContentDescriptors, moderate violence]
-
A.
contentDescriptor
Indicates that something provides a description or characterization of the content of another entity (such as a resource, item, or work).
-
B.
contentTypesRecommended
Indicates that certain types of content are suggested or recommended in relation to a given entity or context.
-
C.
featuredContentType
Indicates the specific type or category of content that is highlighted or promoted as featured.
-
D.
contentDescriptorScope
Indicates the contextual scope or domain within which a particular content descriptor is intended to apply.
-
E.
typicalOnsetDescription
Indicates the usual or characteristic way in which a condition, event, or process begins or first presents itself.
- F. None of above. chosen
Provenance (4 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_69da6275fa6c8190952924930adee150 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e673ab60388190be32cc69bf2b6f76 |
completed | April 20, 2026, 6:42 p.m. |
| PD | Predicate disambiguation | batch_69e55b1b23f88190bdcbe2f81dd226dd |
completed | April 19, 2026, 10:45 p.m. |
| PDg | Predicate description generation | batch_69e56702ad04819099c1c08f28d16809 |
completed | April 19, 2026, 11:36 p.m. |
Created at: April 11, 2026, 11:41 p.m.