Triple
T4035254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ex Machina |
E83811
|
entity |
| Predicate | screenplayDebutOf |
P36923
|
FINISHED |
| Object | Alex Garland as director |
—
|
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: Alex Garland as director | Statement: [Ex Machina, screenplayDebutOf, Alex Garland as director]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: screenplayDebutOf Context triple: [Ex Machina, screenplayDebutOf, Alex Garland as director]
-
A.
filmDebut
Indicates the first film in which an entity (typically a person) appeared or participated, marking their initial entry into film work.
-
B.
featureDirectorialDebutOf
Indicates that a work (typically a film) serves as the first directorial effort of a particular director.
-
C.
screenDebutInMajorRoleFor
Indicates that one entity made their first significant on-screen appearance (major role) in a particular production or work.
-
D.
screenplayWrittenFor
chosen
Indicates that a screenplay was written specifically for a particular film, show, or production.
-
E.
screenDebutInFeatureFilmDirectionFor
Indicates that an entity made their first appearance as a director in a feature film for the specified work.
- 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_69aed92f7cf0819098e0539bdcc3767f |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefb132f6c8190937acd35a6a5a9e4 |
completed | March 9, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69aef8fe440c819093a7fa22c4ff3f1a |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:36 p.m.