Triple
T23340396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beginning of the End |
E591718
|
entity |
| Predicate | directorDescribedAs |
P151930
|
FINISHED |
| Object | cult filmmaker |
—
|
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: cult filmmaker | Statement: [Beginning of the End, directorDescribedAs, cult filmmaker]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directorDescribedAs Context triple: [Beginning of the End, directorDescribedAs, cult filmmaker]
-
A.
director
Indicates that one entity serves as the director (creative or managerial leader) of another entity, such as a film, organization, or project.
-
B.
directorSince
Indicates that one entity has held the role of director for another entity starting from a specified point in time.
-
C.
castingDirectorOf
Indicates that a person serves as the casting director responsible for selecting the cast of a particular production or project.
-
D.
directors
Indicates that one entity serves as a director (or is on the board) of another entity, such as an organization or company.
-
E.
directorFullName
Indicates that the predicate specifies the complete name of the person who serves as the director in the described relationship or context.
- 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_69e25d20e3d08190bcede87673cafb25 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f198329d9c8190992627afa9b54bed |
completed | April 29, 2026, 5:33 a.m. |
| PD | Predicate disambiguation | batch_69effcfd8d288190937a887fe6023c11 |
completed | April 28, 2026, 12:19 a.m. |
| PDg | Predicate description generation | batch_69f01d88b4ec8190a2a17a88e0eda178 |
completed | April 28, 2026, 2:38 a.m. |
Created at: April 17, 2026, 5:18 p.m.