Triple
T30520274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christian martyrs of Durostorum |
E776674
|
entity |
| Predicate | typeOfExecution |
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: [Christian martyrs of Durostorum, typeOfExecution, beheading]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfExecution Context triple: [Christian martyrs of Durostorum, typeOfExecution, beheading]
-
A.
primaryMethodOfExecution
chosen
Indicates the method most commonly or officially used to carry out an execution.
-
B.
executionCoreType
Indicates the specific type or category of execution core (e.g., processing unit or engine) responsible for carrying out a given operation or task.
-
C.
subjectOfExecution
Indicates that one entity is the object or target upon which an execution (carrying out of a death sentence) is performed by another entity.
-
D.
executedIn
Indicates that an action or process is carried out or takes place within a specified location, context, or environment.
-
E.
executionBy
Indicates that one entity carries out or performs the execution (killing or implementation of a death sentence) of 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_69f2249b23c4819087fa85496d92f43f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69ff63e6b61081909c648bf0ff279481 |
completed | May 9, 2026, 4:42 p.m. |
| PD | Predicate disambiguation | batch_69ff6381867881908ae0545df4b71df5 |
completed | May 9, 2026, 4:40 p.m. |
Created at: April 29, 2026, 8:17 p.m.