Triple
T30639696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Collapsing Empire |
E779938
|
entity |
| Predicate | publisherGenreFocus |
P196083
|
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: [The Collapsing Empire, publisherGenreFocus, speculative fiction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publisherGenreFocus Context triple: [The Collapsing Empire, publisherGenreFocus, speculative fiction]
-
A.
publishedGenre
Indicates that an entity has been published in, or is associated with, a particular genre.
-
B.
formerGenreFocus
Indicates that an entity previously concentrated on or specialized in a particular genre, but no longer does so.
-
C.
networkGenreFocus
Indicates that a network primarily centers its content or programming around a particular genre.
-
D.
primarySourceGenre
Indicates the genre or type of creative work that serves as the primary source for something (e.g., an adaptation, derivative work, or related resource).
-
E.
publisherType
Indicates the classification or category of a publisher in relation to a published work or entity.
- F. None of above. chosen
Provenance (4 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_69f224a50ebc81909b961a94c7f66b12 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe066d62b48190867df334039be786 |
completed | May 8, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69fe03afde3c8190a5b9b0778d19eb1a |
completed | May 8, 2026, 3:39 p.m. |
| PDg | Predicate description generation | batch_69fe066b623c819085205fbea901e3cf |
completed | May 8, 2026, 3:51 p.m. |
Created at: April 29, 2026, 8:29 p.m.