Triple
T31732412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Voice of the Fire |
E809894
|
entity |
| Predicate | hasPrologueOrEpilogueBy |
P75062
|
FINISHED |
| Object | Alan Moore |
—
|
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: Alan Moore | Statement: [Voice of the Fire, hasPrologueOrEpilogueBy, Alan Moore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrologueOrEpilogueBy Context triple: [Voice of the Fire, hasPrologueOrEpilogueBy, Alan Moore]
-
A.
hasEpilogueBy
chosen
Indicates that an epilogue of a work is authored, written, or created by a specified agent.
-
B.
hasPrologueInTitle
Indicates that a work’s title explicitly includes the word “Prologue” or a prologue-related phrase.
-
C.
hasPrologueSometimes
Indicates that an entity occasionally or in some instances includes a prologue.
-
D.
hasPrologueCharacter
Indicates that a character appears or is involved in the prologue section of a narrative work.
-
E.
hasPrologueSeries
Indicates that one work serves as a prologue or introductory installment to another work in a series.
- 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_69f348e0e4908190a884582eca646fb7 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a007fc9d9688190af411d5841af34be |
completed | May 10, 2026, 12:53 p.m. |
| PD | Predicate disambiguation | batch_6a007f64813081909a2950336402073b |
completed | May 10, 2026, 12:51 p.m. |
Created at: April 30, 2026, 11:22 p.m.