Triple
T33406982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andy |
E855461
|
entity |
| Predicate | filmScreenwriterOfFirstFilm |
P64760
|
FINISHED |
| Object | Greg Rucka |
—
|
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: Greg Rucka | Statement: [Andy, filmScreenwriterOfFirstFilm, Greg Rucka]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: filmScreenwriterOfFirstFilm Context triple: [Andy, filmScreenwriterOfFirstFilm, Greg Rucka]
-
A.
filmWriterOfWork
chosen
Indicates that a person is the writer or screenwriter responsible for creating the script or written content of a particular film.
-
B.
filmWriterOfWorkAppearedIn
Indicates that a person is the writer of a film in which they themselves also appeared (e.g., as an actor or on-screen participant).
-
C.
hasScreenwriter
Indicates that a creative work is associated with the person or entity who wrote its screenplay or script.
-
D.
directorScreenwriter
Indicates that the person is both the director and the screenwriter of the same film or audiovisual work.
-
E.
hasScreenwriterCreator
Indicates that an entity has another entity serving as the screenwriter who created or originated its screenplay.
- 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_69f3496f04a08190804e56ac5098b8e4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f96badb08190994442c2aba840b1 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:36 a.m.