Triple
T10792126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paul Cameron |
E254606
|
entity |
| Predicate | roleInGoneIn60Seconds |
P19360
|
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: [Paul Cameron, roleInGoneIn60Seconds, director of photography]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInGoneIn60Seconds Context triple: [Paul Cameron, roleInGoneIn60Seconds, director of photography]
-
A.
cultRole
Indicates that an entity holds a specific role, position, or function within a cult or cult-like group.
-
B.
roleInDeaths
Indicates the role or involvement an entity had in causing, contributing to, or being responsible for one or more deaths.
-
C.
roleInScene
Indicates that an entity participates in a particular scene with a specific role or function within that scene.
-
D.
creativeRole
chosen
Indicates that an entity holds a specific creative function or responsibility in relation to another entity, such as a work or project.
-
E.
playsInRole
Indicates that an entity performs or appears in a specific role within a production, event, or context.
- 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_69d6aa609f008190a294200aefcb7bd5 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d732f6dfcc81909096895c588ef46f |
completed | April 9, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69d6f316940c819092a96c429629fdef |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:17 p.m.