Triple
T197806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Simon & Schuster adult trade |
E4035
|
entity |
| Predicate | publishesFormat |
P5128
|
FINISHED |
| Object | hardcover books |
—
|
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: hardcover books | Statement: [Simon & Schuster adult trade, publishesFormat, hardcover books]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publishesFormat Context triple: [Simon & Schuster adult trade, publishesFormat, hardcover books]
-
A.
hasPublishingFormat
chosen
Indicates that an entity is associated with a specific format or medium in which it is published or made publicly available.
-
B.
publishingModel
Indicates the method or framework by which content is produced, distributed, and made publicly available.
-
C.
publishedFor
Indicates that something (such as a work, document, or content) is published with a particular audience, recipient, or target group in mind.
-
D.
format
Indicates the specific arrangement, structure, or presentation style in which something is organized or expressed.
-
E.
publishedIn
Indicates that a work (such as an article, paper, or book) has been formally released or made available within a specific venue, medium, or publication.
- 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_69a254bca59881909a15e1496f1508c7 |
completed | Feb. 28, 2026, 2:36 a.m. |
| NER | Named-entity recognition | batch_69a25be47ea881909c296b30a0d47a65 |
completed | Feb. 28, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69a25b47481c8190add47c641c977bb9 |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:44 a.m.