Triple
T31031590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pénélope |
E790741
|
entity |
| Predicate | hasWorkScreenwriter |
P123411
|
FINISHED |
| Object | Jacques Deray |
—
|
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: Jacques Deray | Statement: [Pénélope, hasWorkScreenwriter, Jacques Deray]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorkScreenwriter Context triple: [Pénélope, hasWorkScreenwriter, Jacques Deray]
-
A.
hasScreenwriter
Indicates that a creative work is associated with the person or entity who wrote its screenplay or script.
-
B.
hasScreenwriterCreator
Indicates that an entity has another entity serving as the screenwriter who created or originated its screenplay.
-
C.
workScreenwritersInclude
chosen
Indicates that a creative work’s credited screenwriters include the specified person or persons.
-
D.
screenwriterOfWork
Indicates that a person served as the screenwriter (wrote the screenplay) for a particular creative work.
-
E.
screenwriterOfWorkCreator
Indicates that one entity is the screenwriter who created or wrote the screenplay for a particular work.
- 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_69f224c97a788190b5da1ead6038a74e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd49f6dbac81909744373a357b7982 |
completed | May 8, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69fd48ed68f481908374183c66a6b055 |
completed | May 8, 2026, 2:22 a.m. |
Created at: April 29, 2026, 8:59 p.m.