Triple
T25545663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teresa Santiago |
E640293
|
entity |
| Predicate | hasWorkDirector |
P32895
|
FINISHED |
| Object | Sam Peckinpah |
—
|
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: Sam Peckinpah | Statement: [Teresa Santiago, hasWorkDirector, Sam Peckinpah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorkDirector Context triple: [Teresa Santiago, hasWorkDirector, Sam Peckinpah]
-
A.
hasDirectorOfWork
Indicates that an entity has a specific person or organization serving as the director responsible for overseeing its work or project.
-
B.
hasWorkBy
Indicates that one entity (such as a collection, exhibition, or publication) includes or contains creative works produced by another entity (such as an artist, author, or creator).
-
C.
basedOnWorkDirector
Indicates that one entity serves as the director of a work on which another entity is based.
-
D.
workDirector
chosen
Indicates that one entity serves as the director (creative or managerial lead) of a particular work or production associated with the other entity.
-
E.
hasWorkCreator
Indicates that an entity is the creator or originator of a particular work (such as a document, artwork, or other creative product).
- 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_69e75dbfff7081909b0aa779d48321d2 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 21, 2026, 3:28 p.m.