Triple
T23264960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Irving v Penguin Books Ltd |
E588119
|
entity |
| Predicate | judgmentResult |
P151594
|
FINISHED |
| Object | claim dismissed |
—
|
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: claim dismissed | Statement: [Irving v Penguin Books Ltd, judgmentResult, claim dismissed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: judgmentResult Context triple: [Irving v Penguin Books Ltd, judgmentResult, claim dismissed]
-
A.
judgmentMessage
Indicates that a message expresses an evaluation, opinion, or decision about a subject or situation.
-
B.
judgmentInvolves
Indicates that a particular judgment, decision, or legal ruling includes, concerns, or pertains to a specified entity or matter.
-
C.
leadingJudgmentBy
Indicates a relationship where one judgment or legal decision is treated as the primary or authoritative basis guiding or influencing another judgment.
-
D.
judgmentContext
Indicates the situational, legal, or evaluative framework within which a judgment or decision is made.
-
E.
judgedAs
Indicates that one entity evaluates or forms an opinion about another entity according to some criteria or standard.
- 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_69e25d148adc819088efbf42672604e9 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f194cc3b908190aaefd036aa2b52b5 |
completed | April 29, 2026, 5:19 a.m. |
| PD | Predicate disambiguation | batch_69effce4d704819092826931d430e8c4 |
completed | April 28, 2026, 12:18 a.m. |
| PDg | Predicate description generation | batch_69f01d8770d081908897c28b04e5faea |
completed | April 28, 2026, 2:37 a.m. |
Created at: April 17, 2026, 4:29 p.m.