Triple
T33479711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Callie Kloves |
E857435
|
entity |
| Predicate | workedOnFilmReleasedBy |
P176664
|
FINISHED |
| Object | Netflix |
—
|
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: Netflix | Statement: [Callie Kloves, workedOnFilmReleasedBy, Netflix]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workedOnFilmReleasedBy Context triple: [Callie Kloves, workedOnFilmReleasedBy, Netflix]
-
A.
hasWorkedOnFilmBy
Indicates that one entity has worked on a film that was created, directed, or otherwise authored by another entity.
-
B.
filmDirectorWorkedWith
Indicates that a film director has collaborated professionally with another person on one or more film projects.
-
C.
workedWithDirector
Indicates that one entity has collaborated professionally with a director on a project or production.
-
D.
associatedWithComposerOfFilm
Indicates a relationship where an entity is connected to the composer who created the musical score for a specific film.
-
E.
workedAsProducerFor
Indicates that one entity served in the role of producer for a work, project, or production associated with 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_69f3497472508190b300ebd3fd402367 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e52e174081908ff9fe1af15586a3 |
completed | May 3, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69f6e3da41948190a4cfe866ce184f73 |
completed | May 3, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69f6e47c13348190a10528c84a401178 |
completed | May 3, 2026, 6 a.m. |
Created at: May 1, 2026, 1:38 a.m.