Triple
T35119951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grishaverse |
E1014138
|
entity |
| Predicate | publisherOfCoreNovels |
P67460
|
FINISHED |
| Object | Macmillan Publishers |
—
|
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: Macmillan Publishers | Statement: [Grishaverse, publisherOfCoreNovels, Macmillan Publishers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publisherOfCoreNovels Context triple: [Grishaverse, publisherOfCoreNovels, Macmillan Publishers]
-
A.
publisherOfNovelization
Indicates that one entity is the publishing company responsible for releasing the novelization version of another entity (such as a film, game, or other work).
-
B.
publisherInUniverse
Indicates that a publisher operates, exists, or is recognized within a particular fictional or conceptual universe.
-
C.
novelPublisher
Indicates that a given publisher is the company or entity responsible for publishing a particular novel.
-
D.
publisherOfStories
Indicates that one entity serves as the publisher responsible for releasing or distributing the stories created by another entity.
-
E.
literarySeriesPublisher
chosen
Indicates the publishing company responsible for producing or releasing a given literary 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_69f76dd8b6948190aaa32b081816bd94 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff6c061c6c81909ff485e9cafc88a2 |
completed | May 9, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69ff6aaf886c8190a3c87d089453f3de |
completed | May 9, 2026, 5:11 p.m. |
Created at: May 3, 2026, 4:01 p.m.