Triple
T34795359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R v Penguin Books Ltd |
E1003061
|
entity |
| Predicate | concernedWorkAuthor |
P129784
|
FINISHED |
| Object | D. H. Lawrence |
—
|
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: D. H. Lawrence | Statement: [R v Penguin Books Ltd, concernedWorkAuthor, D. H. Lawrence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: concernedWorkAuthor Context triple: [R v Penguin Books Ltd, concernedWorkAuthor, D. H. Lawrence]
-
A.
basedOnWorkAuthorAssociatedWith
Indicates that one entity is derived from or related to a work whose author is associated with another specified entity.
-
B.
centralWorkAuthor
Indicates that an author is the primary creator or main writer responsible for a central or key work.
-
C.
associatedWithAuthorWork
Indicates a relationship where an author is connected to a work they created, contributed to, or are otherwise credited for.
-
D.
subjectOfWorkBy
chosen
Indicates that one entity is the main topic or focus of a work (such as a book, article, or artwork) created by another entity.
-
E.
associatedWithWorkOf
Indicates that one entity has a connection or involvement with the work, creation, or output produced by another entity.
- 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_69f76db543808190b188c6c86a91491b |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8cec6d48190bebfa884b2f938c0 |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 3:59 p.m.