Triple
T3850837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R v Thorpe and Others (1979) |
E85290
|
entity |
| Predicate | hasAccusedRole |
P51934
|
FINISHED |
| Object | former Liberal Party leader |
—
|
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: former Liberal Party leader | Statement: [R v Thorpe and Others (1979), hasAccusedRole, former Liberal Party leader]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAccusedRole Context triple: [R v Thorpe and Others (1979), hasAccusedRole, former Liberal Party leader]
-
A.
hasAccuser
Indicates that one entity serves as the accuser of another entity in a dispute, complaint, or allegation.
-
B.
accusedIn
Indicates that a person or entity is formally charged with wrongdoing in a particular case, proceeding, or context.
-
C.
accusedOf
Indicates that one entity has formally alleged or claimed that another entity committed a specific wrongdoing or offense.
-
D.
hasAccusedAssassin
Indicates that one entity has formally or informally claimed that another entity is the assassin responsible for a killing.
-
E.
accusationType
Indicates the specific category or nature of an accusation made by one party against another.
- 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_69aed936de1c81908f91bed80f70abb2 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeebcf67788190975105131baabc4b |
completed | March 9, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69aee750377c8190af70c79768c0edd8 |
completed | March 9, 2026, 3:29 p.m. |
| PDg | Predicate description generation | batch_69aee8d9b328819080158be59e5bcc97 |
completed | March 9, 2026, 3:35 p.m. |
Created at: March 9, 2026, 3:19 p.m.