Triple
T21148649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Everard Digby |
E521125
|
entity |
| Predicate | plotObjective |
P56726
|
FINISHED |
| Object | blow up the House of Lords |
—
|
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: blow up the House of Lords | Statement: [Everard Digby, plotObjective, blow up the House of Lords]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plotObjective Context triple: [Everard Digby, plotObjective, blow up the House of Lords]
-
A.
actorObjective
chosen
Indicates that an actor has a specific goal, purpose, or intended outcome in relation to another entity or situation.
-
B.
axisObjective
Indicates that an entity serves as a primary goal, target, or focal objective along a defined axis or strategic direction in a given context.
-
C.
usesObjective
Indicates that an agent employs or applies a particular object, tool, or resource to carry out an action or achieve a goal.
-
D.
aimOf
Indicates that one entity serves as the goal, purpose, or intended target of another entity’s action, plan, or existence.
-
E.
gameObjective
Indicates the primary goal or intended outcome that participants aim to achieve within a game.
- 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_69e0b50c6a848190a4e525a77a319b8a |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e723ffb578819080a000987459a8a5 |
completed | April 21, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69e5f5f8a5bc819081918c7fa8e4496d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 2:58 p.m.