Triple
T6189963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amir Mokri |
E138159
|
entity |
| Predicate | roleInFast & Furious |
P21967
|
FINISHED |
| Object | director of photography |
—
|
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: director of photography | Statement: [Amir Mokri, roleInFast & Furious, director of photography]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInFast & Furious Context triple: [Amir Mokri, roleInFast & Furious, director of photography]
-
A.
roleInFilmEcosystem
Indicates the specific function or position an entity holds within the broader network of activities, stakeholders, and processes that make up the film ecosystem.
-
B.
playsInRole
Indicates that an entity performs or appears in a specific role within a production, event, or context.
-
C.
roleInFranchiseHistory
Indicates the specific function, position, or contribution an entity has within the historical development or timeline of a franchise.
-
D.
roleInGang
Indicates that an entity holds a specific position or function within a gang organization.
-
E.
hasCrewRole
chosen
Indicates that an entity serves in a specific role or position within a crew associated with another entity.
- 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_69c008a8fd408190b7ec6e42934974a6 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0621abad48190acb9ec019c065ed4 |
completed | March 22, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69c055fa0a808190bda37832e3ac150c |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:19 p.m.