Triple
T9620526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Penguin General |
E232329
|
entity |
| Predicate | hasPublishingProgramme |
P75827
|
FINISHED |
| Object | hardback 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: hardback books | Statement: [Penguin General, hasPublishingProgramme, hardback books]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPublishingProgramme Context triple: [Penguin General, hasPublishingProgramme, hardback books]
-
A.
hasPublishingProgram
chosen
Indicates that an entity operates or maintains a formal program or initiative for publishing content, works, or materials.
-
B.
hasProgramme
Indicates that an entity is associated with or offers a particular programme (such as a course of study, plan, or structured set of activities).
-
C.
hasPublication
Indicates that an entity is associated with or responsible for a specific publication.
-
D.
hasPublisher
Indicates that an entity is published or issued by a specific publisher.
-
E.
hasContributorProgram
Indicates that an entity operates or participates in a formal program through which contributors can submit work, content, or support.
- 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_69ca84867bb88190b4b57dd5a56d5691 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9ad3a8d88190b1414aa676d82f36 |
completed | April 1, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69ccd5aa1d2c8190a287bf1cf4a3037e |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:09 p.m.