Triple
T24780612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charles Grady |
E619984
|
entity |
| Predicate | hasAuthorialSource |
P45645
|
FINISHED |
| Object | Stephen King’s novel The Shining (1977) |
—
|
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: Stephen King’s novel The Shining (1977) | Statement: [Charles Grady, hasAuthorialSource, Stephen King’s novel The Shining (1977)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAuthorialSource Context triple: [Charles Grady, hasAuthorialSource, Stephen King’s novel The Shining (1977)]
-
A.
hasAuthorOfSourceMaterial
Indicates that one entity is the creator or writer of the original source material on which another entity is based.
-
B.
hasSourceWork
chosen
Indicates that something originates from, is derived from, or is based on a particular source work.
-
C.
hasAuthorialBackground
Indicates that an entity has a creator or author with a specific background, context, or set of characteristics associated with them.
-
D.
hasAuthor
Indicates that an entity is written or created by a specific author.
-
E.
originalAuthorOfSource
Indicates that an entity is the original creator or author of a given source or 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_69e2fabdbe8c8190adbb9434b8636cad |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f42d9000b8819081ea2605f3c193d6 |
completed | May 1, 2026, 4:35 a.m. |
| PD | Predicate disambiguation | batch_69f420f471a0819095a6cd24ed8f7476 |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 4:44 a.m.