Triple
T36146255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dragon Pictures |
E1045459
|
entity |
| Predicate | collaboratedOnFilmWith |
P183306
|
FINISHED |
| Object | Channel 4 Films |
—
|
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: Channel 4 Films | Statement: [Dragon Pictures, collaboratedOnFilmWith, Channel 4 Films]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collaboratedOnFilmWith Context triple: [Dragon Pictures, collaboratedOnFilmWith, Channel 4 Films]
-
A.
workedOnFilmReleasedBy
Indicates that one entity contributed work to a film that was distributed or released by another entity.
-
B.
hasWorkedOnFilmBy
Indicates that one entity has worked on a film that was created, directed, or otherwise authored by another entity.
-
C.
coProducesFilmWith
chosen
Indicates a collaborative relationship in which two or more entities jointly produce the same film.
-
D.
filmDirectorWorkedWith
Indicates that a film director has collaborated professionally with another person on one or more film projects.
-
E.
partOfFilmographyOf
Indicates that a work (such as a film, show, or role) is included in the body of screen-related works credited to a particular person.
- 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_69f76e37ace88190a906b107d388f5d1 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:08 p.m.