Triple
T23264956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Irving v Penguin Books Ltd |
E588119
|
entity |
| Predicate | claimByPlaintiff |
P106534
|
FINISHED |
| Object | alleged libel |
—
|
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: alleged libel | Statement: [Irving v Penguin Books Ltd, claimByPlaintiff, alleged libel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: claimByPlaintiff Context triple: [Irving v Penguin Books Ltd, claimByPlaintiff, alleged libel]
-
A.
legalClaimBy
chosen
Indicates that a specific party initiates or holds a legal claim against another party or concerning a particular matter.
-
B.
claim1
Indicates that an entity asserts, alleges, or maintains the truth of a particular statement, proposition, or fact.
-
C.
makesClaim
Indicates that one entity asserts, states, or puts forward a claim about another entity or about some proposition.
-
D.
claimedSee
Indicates that one entity asserted or reported having seen or visually perceived another entity or event.
-
E.
lostClaimTo
Indicates that one entity previously held a right or ownership over something but no longer retains that claim, often due to transfer, forfeiture, or invalidation.
- 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_69e25d148adc819088efbf42672604e9 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f194cb76c48190869915cd93b44fcc |
completed | April 29, 2026, 5:19 a.m. |
| PD | Predicate disambiguation | batch_69effce4d704819092826931d430e8c4 |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:29 p.m.