Triple
T1905938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chatto & Windus |
E38003
|
entity |
| Predicate | hasImprintStatus |
P33833
|
FINISHED |
| Object | imprint within Penguin Random House UK |
—
|
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: imprint within Penguin Random House UK | Statement: [Chatto & Windus, hasImprintStatus, imprint within Penguin Random House UK]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasImprintStatus Context triple: [Chatto & Windus, hasImprintStatus, imprint within Penguin Random House UK]
-
A.
hasImprintType
Indicates that an entity (such as a publication or product) is associated with a specific type or category of imprint.
-
B.
hasImprintRole
Indicates that an entity holds a specific role or function in relation to the imprinting or publication details of another entity.
-
C.
hasImprimatur
Indicates that an entity has received official approval or authorization, typically from a recognized authority.
-
D.
hasParentImprint
Indicates that one publishing imprint is the parent or controlling imprint of another imprint.
-
E.
hasPrintVersion
Indicates that one entity exists or is available as a printed or physical edition of another 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_69a8862a26088190aae5243695aeefc0 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb34d94fc8190a5bf1e582c77c725 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abafe9f8b0819086d8f6288511c66d |
completed | March 7, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69abb34c4a64819096e12b152b84c334 |
completed | March 7, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:35 p.m.