Triple
T34342866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liz Blake |
E881341
|
entity |
| Predicate | hasScreenWriterCreator |
P80863
|
FINISHED |
| Object | Brian De Palma |
—
|
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: Brian De Palma | Statement: [Liz Blake, hasScreenWriterCreator, Brian De Palma]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScreenWriterCreator Context triple: [Liz Blake, hasScreenWriterCreator, Brian De Palma]
-
A.
hasScreenwriterCreator
chosen
Indicates that an entity has another entity serving as the screenwriter who created or originated its screenplay.
-
B.
hasScreenwriter
Indicates that a creative work is associated with the person or entity who wrote its screenplay or script.
-
C.
screenwriterCreatedBy
Indicates that a screenwriter was created, conceived, or brought into existence by a particular entity (such as a person, organization, or work).
-
D.
screenwriterOfWorkCreator
Indicates that one entity is the screenwriter who created or wrote the screenplay for a particular work.
-
E.
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).
- 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_69f349bc55e881908c8e338ef76b0043 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd231cab588190ad0953dc8f4af8f2 |
completed | May 7, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69fd1aa3f1c481909fe6e9cab1383551 |
completed | May 7, 2026, 11:05 p.m. |
Created at: May 1, 2026, 1:58 a.m.