Triple
T14688468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Voyager Books |
E344974
|
entity |
| Predicate | publisherOfGenre |
P26454
|
FINISHED |
| Object | speculative fiction |
—
|
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: speculative fiction | Statement: [Voyager Books, publisherOfGenre, speculative fiction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publisherOfGenre Context triple: [Voyager Books, publisherOfGenre, speculative fiction]
-
A.
publisherType
Indicates the classification or category of a publisher in relation to a published work or entity.
-
B.
publisherOfSeries
Indicates that an entity serves as the publishing organization responsible for producing or distributing a particular series.
-
C.
publishedGenre
chosen
Indicates that an entity has been published in, or is associated with, a particular genre.
-
D.
publisherInUniverse
Indicates that a publisher operates, exists, or is recognized within a particular fictional or conceptual universe.
-
E.
publisherForMajorTitles
Indicates that an entity serves as the primary publisher responsible for releasing another entity’s major or most significant titles.
- 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_69d822e34b348190ada4d1cdb6c7c226 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb5844de481908a796eaa474bfde9 |
completed | April 14, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69de6579fb7881909becc8f5822b39d4 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:28 a.m.