Triple
T34795355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R v Penguin Books Ltd |
E1003061
|
entity |
| Predicate | publisherDefendant |
P199843
|
FINISHED |
| Object | Penguin Books |
—
|
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: Penguin Books | Statement: [R v Penguin Books Ltd, publisherDefendant, Penguin Books]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publisherDefendant Context triple: [R v Penguin Books Ltd, publisherDefendant, Penguin Books]
-
A.
publisherEditor
Indicates a relationship where one entity serves as the editor responsible for the content published by another entity acting as the publisher.
-
B.
publisherOfWorkAppearingIn
Indicates that an entity is the publisher responsible for issuing a work in which another specified work appears (e.g., as part of a collection, volume, or compilation).
-
C.
publisherOfWorks
Indicates that one entity serves as the publisher responsible for issuing or distributing the works created by another entity.
-
D.
publisherType
Indicates the classification or category of a publisher in relation to a published work or entity.
-
E.
formerPublisher
Indicates that one entity previously served as the publisher of another entity but no longer holds that role.
- 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_69f76db543808190b188c6c86a91491b |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69ff5b233e9c8190adc06cca0758986b |
completed | May 9, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69ff5a5682108190a006b23c4fcdcc7c |
completed | May 9, 2026, 4:01 p.m. |
| PDg | Predicate description generation | batch_69ff5b224b8c8190bd0955876098ecc8 |
completed | May 9, 2026, 4:04 p.m. |
Created at: May 3, 2026, 3:59 p.m.