Triple
T26700803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Evan Baxter |
E673148
|
entity |
| Predicate | screenwriterForWork |
P25235
|
FINISHED |
| Object | Steve Oedekerk |
—
|
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: Steve Oedekerk | Statement: [Evan Baxter, screenwriterForWork, Steve Oedekerk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: screenwriterForWork Context triple: [Evan Baxter, screenwriterForWork, Steve Oedekerk]
-
A.
screenwriterOfWork
chosen
Indicates that a person served as the screenwriter (wrote the screenplay) for a particular creative work.
-
B.
screenwriterCreator
Indicates that one entity is the screenwriter who created or authored the screenplay for another entity (such as a film, episode, or audiovisual work).
-
C.
screenwriterOfWorkCreator
Indicates that one entity is the screenwriter who created or wrote the screenplay for a particular work.
-
D.
screenwriters
Indicates that one or more entities are the writers who authored the screenplay or script for a film, show, or similar work.
-
E.
screenwriterOfWorkAppearingIn
Indicates that a person is the screenwriter of a work in which a specified entity (such as a character, actor, or role) appears.
- 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_69eecda2b49c8190a6c481cfc4c07954 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f6177ef08481908130a8cc2ec33fb2 |
completed | May 2, 2026, 3:25 p.m. |
| PD | Predicate disambiguation | batch_69f60b8bb0d08190ab5a9a2a8847c6f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 3:31 a.m.