Triple
T33954243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ESRB T |
E870521
|
entity |
| Predicate | governsContentAreas |
P58064
|
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: [ESRB T, governsContentAreas, violence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governsContentAreas Context triple: [ESRB T, governsContentAreas, violence]
-
A.
governanceArea
Indicates the geographic or jurisdictional area over which an entity has governing authority or responsibility.
-
B.
governsGeneralEducationFor
Indicates that one entity has authority over and is responsible for setting or managing the general education requirements or curriculum for another entity.
-
C.
examContentArea
Indicates that an exam includes or focuses on a particular content area or subject domain.
-
D.
governedTopic
chosen
Indicates that a governing entity exercises authority, control, or regulatory oversight over a particular topic, issue, or domain.
-
E.
sectorGoverned
Indicates that a particular sector or domain is under the authority, control, or regulatory oversight of a specified governing entity.
- 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_69f3499c2d7481909c953a5010227725 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a00c3362dcc819096e49b882709fddd |
completed | May 10, 2026, 5:41 p.m. |
| PD | Predicate disambiguation | batch_6a00c2e5cdd88190a5f2d0f6a843cd56 |
completed | May 10, 2026, 5:39 p.m. |
Created at: May 1, 2026, 1:49 a.m.