Triple
T19685589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Court of Justice for the trial of Charles I |
E472702
|
entity |
| Predicate | methodOfExecutionOrdered |
P90968
|
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: [High Court of Justice for the trial of Charles I, methodOfExecutionOrdered, beheading]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: methodOfExecutionOrdered Context triple: [High Court of Justice for the trial of Charles I, methodOfExecutionOrdered, beheading]
-
A.
previousMethodOfExecution
Indicates that one method of execution was used before another in a temporal sequence.
-
B.
executionOrderedAtRequestOf
chosen
Indicates that an execution was carried out according to the wishes or formal request made by a specific party.
-
C.
primaryMethodOfExecution
Indicates the method most commonly or officially used to carry out an execution.
-
D.
previousExecutionMethod
Indicates that one entity was formerly used as the method or means by which the other entity was executed.
-
E.
notableExecutionMethod
Indicates that a particular method or manner of execution is especially notable or characteristic in relation to the subject.
- 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_69d8e515bef88190bc30781aea50537a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e641c33b94819081bdeb56910f6ff8 |
completed | April 20, 2026, 3:09 p.m. |
| PD | Predicate disambiguation | batch_69e53039ea808190a9106a53f564ab92 |
completed | April 19, 2026, 7:42 p.m. |
Created at: April 10, 2026, 1:45 p.m.