Triple
T32808583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earls of Derwentwater |
E839082
|
entity |
| Predicate | thirdEarlExecutionMethod |
P106448
|
FINISHED |
| Object | beheading |
—
|
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: beheading | Statement: [Earls of Derwentwater, thirdEarlExecutionMethod, beheading]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thirdEarlExecutionMethod Context triple: [Earls of Derwentwater, thirdEarlExecutionMethod, beheading]
-
A.
thirdActFunction
Indicates the narrative role or purpose that an element (such as a character, event, or device) serves specifically within the third act of a story or dramatic structure.
-
B.
primaryMethodOfExecution
chosen
Indicates the method most commonly or officially used to carry out an execution.
-
C.
keyExecutionMethod
Indicates the method or process by which a key (e.g., cryptographic or access key) is applied, used, or executed in a given context.
-
D.
executionBy
Indicates that one entity carries out or performs the execution (killing or implementation of a death sentence) of another entity.
-
E.
methodOfExecutionChallenged
Indicates that a legal action contests or disputes the specific method by which an execution is to be carried out.
- 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_69f3493d35208190b4351b4e85f2fa16 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 1, 2026, 1:15 a.m.