Triple
T11705111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ESRB E10+ |
E278218
|
entity |
| Predicate | contentDescriptorScope |
P101344
|
FINISHED |
| Object | mild 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: mild violence | Statement: [ESRB E10+, contentDescriptorScope, mild violence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contentDescriptorScope Context triple: [ESRB E10+, contentDescriptorScope, mild violence]
-
A.
scopeType
Indicates the specific range, level, or context within which a given relationship, rule, or action is defined or applies.
-
B.
conceptualScope
Indicates the range or domain of ideas, concepts, or topics that something (such as a work, theory, or term) is intended to cover or address.
-
C.
acquisitionScope
Indicates the extent, boundaries, or coverage of what is obtained or brought under control through an acquisition.
-
D.
contentAccess
Indicates that one entity is permitted to retrieve, view, or otherwise use the content provided or controlled by another entity.
-
E.
scopeDetail
Indicates a more specific or refined characterization of the extent, boundaries, or coverage of something within a broader scope.
- 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_69d6aaff2ce88190b4a1e4b341ad5377 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a49c8c38819083d83f5fdec52b7f |
completed | April 10, 2026, 7:19 a.m. |
| PD | Predicate disambiguation | batch_69d88a7b30948190b616a9db5c5488d5 |
completed | April 10, 2026, 5:28 a.m. |
| PDg | Predicate description generation | batch_69d89546a8688190b51455b5e12caf91 |
completed | April 10, 2026, 6:14 a.m. |
Created at: April 8, 2026, 9:40 p.m.