Triple
T25711577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tyburn gallows |
E644745
|
entity |
| Predicate | typicalExecutionMethod |
P106448
|
FINISHED |
| Object | short-drop hanging |
—
|
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: short-drop hanging | Statement: [Tyburn gallows, typicalExecutionMethod, short-drop hanging]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalExecutionMethod Context triple: [Tyburn gallows, typicalExecutionMethod, short-drop hanging]
-
A.
primaryMethodOfExecution
chosen
Indicates the method most commonly or officially used to carry out an execution.
-
B.
notableExecutionMethod
Indicates that a particular method or manner of execution is especially notable or characteristic in relation to the subject.
-
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.
previousMethodOfExecution
Indicates that one method of execution was used before another in a temporal sequence.
-
E.
orderedExecutionMethod
Indicates that one method or process must be executed in a specific sequence relative to others.
- 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_69e77e83c8ec8190bf52fcdac4838984 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69fd76d1e5208190a6f26651492d1e3c |
completed | May 8, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69fd702a226c81908edfda00f4be4130 |
completed | May 8, 2026, 5:10 a.m. |
Created at: April 21, 2026, 9:14 p.m.