Triple
T36764585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robert Davis |
E908298
|
entity |
| Predicate | characterInDirector |
P201024
|
FINISHED |
| Object | William A. Seiter |
—
|
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: William A. Seiter | Statement: [Robert Davis, characterInDirector, William A. Seiter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: characterInDirector Context triple: [Robert Davis, characterInDirector, William A. Seiter]
-
A.
directorCharacterOf
Indicates that a director is responsible for directing a particular character in a work (e.g., film, TV show, or play).
-
B.
characterIn
Indicates that an entity appears as a character within a specified work, story, or narrative.
-
C.
associatedWithDirectorCharacter
Indicates a relationship where something is linked to or connected with a director character, typically signifying involvement, relevance, or attribution to that director character.
-
D.
directorCharacterName
Indicates that the specified name is the character name used by the director (or representing the director) within a work.
-
E.
characterPerformer
Indicates that a performer portrays or voices a particular character in a work.
- F. None of above. chosen
Provenance (4 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_69f76e786ba481909cdcf6cf6b39dd32 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ffc1550cb481908628e446d9b67f7b |
completed | May 9, 2026, 11:20 p.m. |
| PD | Predicate disambiguation | batch_69ffc10a74708190ae90e2c378791f70 |
completed | May 9, 2026, 11:19 p.m. |
| PDg | Predicate description generation | batch_69ffc15434c8819093aa3b33813613be |
completed | May 9, 2026, 11:20 p.m. |
Created at: May 3, 2026, 4:12 p.m.