Triple
T35016924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Simon & Marcy |
E1010078
|
entity |
| Predicate | writtenAndStoryboardedBy |
P25235
|
FINISHED |
| Object | Cole Sanchez |
—
|
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: Cole Sanchez | Statement: [Simon & Marcy, writtenAndStoryboardedBy, Cole Sanchez]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writtenAndStoryboardedBy Context triple: [Simon & Marcy, writtenAndStoryboardedBy, Cole Sanchez]
-
A.
screenplayCoWrittenWith
Indicates that two or more individuals collaborated to write the same screenplay.
-
B.
screenwriterOfWork
chosen
Indicates that a person served as the screenwriter (wrote the screenplay) for a particular creative work.
-
C.
screenwriterOfWorkCreator
Indicates that one entity is the screenwriter who created or wrote the screenplay for a particular work.
-
D.
screenwriterCreatedBy
Indicates that a screenwriter was created, conceived, or brought into existence by a particular entity (such as a person, organization, or work).
-
E.
actuallyWrittenBy
Indicates that the specified work was in fact authored by the given entity, possibly correcting or overriding a previously assumed or credited author.
- 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_69f76dcc3ac8819096a3ed52f5fa2523 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7858aa5508190a07dde993b3356fc |
completed | May 3, 2026, 5:27 p.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.