Triple
T24920470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Book of Dust |
E624106
|
entity |
| Predicate | intendedNumberOfVolumes |
P85593
|
FINISHED |
| Object | 3 |
—
|
LITERAL FINISHED |
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: 3 | Statement: [The Book of Dust, intendedNumberOfVolumes, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedNumberOfVolumes Context triple: [The Book of Dust, intendedNumberOfVolumes, 3]
-
A.
numberOfVolumes
Indicates the total count of separate volumes or parts that make up a multi-volume work or collection.
-
B.
intendedNumberOfBooks
chosen
Indicates the number of books that an agent plans or aims to have, produce, read, or otherwise be associated with, as opposed to the number actually realized.
-
C.
expectedDataVolume
Indicates the anticipated amount of data that should be produced, transferred, or stored in the context of the specified relationship or process.
-
D.
hasThreeVolumeStructureRole
Indicates that an entity participates in or fulfills a role within a three-volume structural organization or framework.
-
E.
volumeIdentifierLengthLimit
Indicates the maximum allowed length for a volume’s identifier within a given system or context.
- 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_69f5f6baf2d48190a6a4cd6501be87d2 |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f5afd5baac8190bb8ed576813c8591 |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 18, 2026, 5:28 a.m.