Triple
T24920457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Book of Dust |
E624106
|
entity |
| Predicate | mainProtagonistOfSecondVolume |
P9202
|
FINISHED |
| Object | Lyra Belacqua |
—
|
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: Lyra Belacqua | Statement: [The Book of Dust, mainProtagonistOfSecondVolume, Lyra Belacqua]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainProtagonistOfSecondVolume Context triple: [The Book of Dust, mainProtagonistOfSecondVolume, Lyra Belacqua]
-
A.
hasProtagonistInFirstVolume
Indicates that a work’s first volume features a specific entity as its main character.
-
B.
secondaryProtagonistType
Indicates the role or category of a work’s secondary main character in relation to the primary protagonist.
-
C.
mainProtagonist
chosen
Indicates that the subject is the central character or primary focus in the narrative of the related work.
-
D.
hasSecondaryProtagonist
Indicates that an entity (such as a work of fiction) features another character who serves as a secondary or supporting main protagonist alongside the primary one.
-
E.
laterMainCharacterOf
Indicates that one entity becomes the main character of a work at a later point in time, succeeding another main character.
- 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_69e2fac889c081908e9ff686cb428e5a |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d77f6e88190a4643ab2cbef567b |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 5:28 a.m.