Triple
T35053355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cassie |
E1011392
|
entity |
| Predicate | createdByDirectorChoreographer |
P199963
|
FINISHED |
| Object | Michael Bennett |
—
|
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: Michael Bennett | Statement: [Cassie, createdByDirectorChoreographer, Michael Bennett]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createdByDirectorChoreographer Context triple: [Cassie, createdByDirectorChoreographer, Michael Bennett]
-
A.
hasDirectorCreator
Indicates that an entity has a person or organization who directed or created it (e.g., a film’s director or a work’s creator).
-
B.
hasDirectorScreenwriter
Indicates that a director is also the screenwriter (or one of the screenwriters) for a given work.
-
C.
createdForFilmDirectedBy
Indicates that something (such as a work or contribution) was specifically created for a film that was directed by a particular person.
-
D.
hasAuthorDirector
Indicates that an entity (such as a work or production) has a person who serves in both the roles of author and director for it.
-
E.
hasArtistDirector
Indicates that one entity serves as the artist director (artistic leader or creative head) of another entity.
- 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_69f76dcfdda48190b1ebae5da8b54f12 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff65987ff88190b09be64f7c0e1da9 |
completed | May 9, 2026, 4:49 p.m. |
| PD | Predicate disambiguation | batch_69ff6525b0548190bef7a9f009e00bb8 |
completed | May 9, 2026, 4:47 p.m. |
| PDg | Predicate description generation | batch_69ff659717708190bb56714d1b261063 |
completed | May 9, 2026, 4:49 p.m. |
Created at: May 3, 2026, 4:01 p.m.