Triple
T13600653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Born Free |
E324931
|
entity |
| Predicate | musicVideoContainsGraphicViolence |
P107612
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Born Free, musicVideoContainsGraphicViolence, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: musicVideoContainsGraphicViolence Context triple: [Born Free, musicVideoContainsGraphicViolence, yes]
-
A.
containsGraphicViolence
Indicates that the subject includes depictions of explicit, intense, or realistic physical harm or brutality.
-
B.
containsViolence
chosen
Indicates that the subject includes, depicts, or involves acts of physical harm, aggression, or violent behavior.
-
C.
musicVideoFor
Indicates that one entity is a music video created to accompany, represent, or promote another entity, typically a song or musical work.
-
D.
hasMusicVideo
Indicates that a piece of media (typically a song) is associated with or accompanied by a music video.
-
E.
musicVideoProject
Indicates a relationship where an entity is involved in, associated with, or serves as a project for creating or producing a music video.
- 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_69d80769eaf081909d82f44e484d6113 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb07ad3f48190a2173e42c5cfedb1 |
completed | April 12, 2026, 2:47 p.m. |
| PD | Predicate disambiguation | batch_69dbae18eaf48190809e8b365856cde9 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:49 p.m.