Triple
T34339322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dead Meat |
E881241
|
entity |
| Predicate | hasDirectorWithNotableWorkIn |
P166250
|
FINISHED |
| Object | music videos |
—
|
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: music videos | Statement: [Dead Meat, hasDirectorWithNotableWorkIn, music videos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDirectorWithNotableWorkIn Context triple: [Dead Meat, hasDirectorWithNotableWorkIn, music videos]
-
A.
hasDirectorOfWork
Indicates that an entity has a specific person or organization serving as the director responsible for overseeing its work or project.
-
B.
hasDirectorInKeyWork
Indicates that a director is associated with a key or primary work of an entity (such as a film, series, or major production).
-
C.
workOfDirectorKnownFor
chosen
Indicates that a work (such as a film or show) is directed by a person for whom this work is one of their notable or best-known creations.
-
D.
notableDirector
Indicates that a person has directed a work (such as a film or show) in a way that is recognized as significant or distinguished.
-
E.
hasDirectorStar
Indicates that a person both directed and starred in the same work (e.g., film, show, or production).
- 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_69f349bc55e881908c8e338ef76b0043 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff0d80c0dc81909fbd12285c7a45c0 |
completed | May 9, 2026, 10:33 a.m. |
| PD | Predicate disambiguation | batch_69ff0cd03e78819094895058f925fbfa |
completed | May 9, 2026, 10:30 a.m. |
Created at: May 1, 2026, 1:58 a.m.