Triple
T27051627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cheyenne’s Theme |
E684786
|
entity |
| Predicate | hasAssociatedDirector |
P112294
|
FINISHED |
| Object | Sergio Leone |
—
|
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: Sergio Leone | Statement: [Cheyenne’s Theme, hasAssociatedDirector, Sergio Leone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAssociatedDirector Context triple: [Cheyenne’s Theme, hasAssociatedDirector, Sergio Leone]
-
A.
hasDirectorOfWork
chosen
Indicates that an entity has a specific person or organization serving as the director responsible for overseeing its work or project.
-
B.
hasAssociatedFranchiseViaDirector
Indicates that an entity is associated with a franchise through the involvement of a director who connects the entity to that franchise.
-
C.
hasDirectorInKeyWork
Indicates that a director is associated with a key or primary work of an entity (such as a film, series, or major production).
-
D.
hasDirectorStar
Indicates that a person both directed and starred in the same work (e.g., film, show, or production).
-
E.
hasDirectorCreator
Indicates that an entity has a person or organization who directed or created it (e.g., a film’s director or a work’s creator).
- 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_69ef14829fac8190914bef9ecc3005d7 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 27, 2026, 8:14 a.m.