Triple
T28924085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isaac Morris |
E733596
|
entity |
| Predicate | deathPlannedBy |
P169061
|
FINISHED |
| Object | Justice Lawrence Wargrave |
—
|
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: Justice Lawrence Wargrave | Statement: [Isaac Morris, deathPlannedBy, Justice Lawrence Wargrave]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deathPlannedBy Context triple: [Isaac Morris, deathPlannedBy, Justice Lawrence Wargrave]
-
A.
plansToMurder
chosen
Indicates that one entity intends and has formed a plan to unlawfully kill another entity.
-
B.
deathBy
Indicates a relationship where one entity’s death is caused by another entity, event, or factor.
-
C.
allegedToHaveKilled
Indicates that one entity is claimed or accused, but not proven, to have killed another entity.
-
D.
assassinatedIn
Indicates that an assassination of one entity occurred within the specified location or context represented by another entity.
-
E.
threatenedToKill
Indicates that one entity has made a threat or expressed an intention to kill 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_69f05b0a5cc0819094828367ae204b70 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f6978fe97081908fe568091ad9b159 |
completed | May 3, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 28, 2026, 8:22 a.m.