Triple
T27607685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eartha Kitt as Yzma |
E700223
|
entity |
| Predicate | directedByWork |
P7373
|
FINISHED |
| Object | MarkDindal |
—
|
NE NERFINISHED |
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: MarkDindal | Statement: [Eartha Kitt as Yzma, directedByWork, MarkDindal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directedByWork Context triple: [Eartha Kitt as Yzma, directedByWork, MarkDindal]
-
A.
basedOnWorkDirector
Indicates that one entity serves as the director of a work on which another entity is based.
-
B.
workDirector
Indicates that one entity serves as the director (creative or managerial lead) of a particular work or production associated with the other entity.
-
C.
directed
chosen
Indicates that one entity served as the director or guiding authority responsible for overseeing and controlling the actions or production involving another entity.
-
D.
directedTo
Indicates that something is sent, aimed, or addressed toward a particular target or recipient.
-
E.
performedInWorkBy
Indicates that an action or role was carried out within a specific work (e.g., a film, book, or composition) by a particular agent or contributor.
- 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_69ef6a4e2e208190b63b7268f405785c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f71f8ee0688190bd025f27993452d3 |
completed | May 3, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
Created at: April 27, 2026, 2:10 p.m.