Triple
T33294952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chisum |
E852413
|
entity |
| Predicate | starsCharacterPlayedBy |
P9616
|
FINISHED |
| Object | John Wayne as John Chisum |
—
|
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: John Wayne as John Chisum | Statement: [Chisum, starsCharacterPlayedBy, John Wayne as John Chisum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: starsCharacterPlayedBy Context triple: [Chisum, starsCharacterPlayedBy, John Wayne as John Chisum]
-
A.
playedBy
chosen
Indicates that a role, character, or performance is portrayed or executed by a specific person or agent.
-
B.
directorCharacterOf
Indicates that a director is responsible for directing a particular character in a work (e.g., film, TV show, or play).
-
C.
filmCharacterOf
Indicates that a person or character is a character appearing in a specified film.
-
D.
worksForCharacterPlayedBy
Indicates that one character is employed by, or works under, another character who is portrayed by a specific actor.
-
E.
characterInPlayBy
Indicates that a character appears in or is part of a play authored or created by a specific person.
- 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_69f34966ed4c81908dc9dda82d8c7fe3 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6e3156ea48190b604e414665ef351 |
completed | May 3, 2026, 5:54 a.m. |
| PD | Predicate disambiguation | batch_69f6de0b9ba48190887c9eb5d06a2e94 |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:33 a.m.