Triple
T906050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ignatius of Antioch |
E19550
|
entity |
| Predicate | martyrdom |
P13133
|
FINISHED |
| Object | Executed in Rome |
—
|
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: Executed in Rome | Statement: [Ignatius of Antioch, martyrdom, Executed in Rome]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: martyrdom Context triple: [Ignatius of Antioch, martyrdom, Executed in Rome]
-
A.
martyrdomStatus
Indicates the state or condition of an entity with respect to being recognized or regarded as a martyr.
-
B.
sacrifice
Indicates giving up something of value, often for the benefit, protection, or advantage of another entity or goal.
-
C.
methodOfPersecution
chosen
Indicates the specific means, technique, or process by which an act of persecution is carried out.
-
D.
notableVictim
Indicates that the subject is a person or entity who is notably recognized as a victim of the object (such as an event, crime, or harmful action).
-
E.
notableVictims
Indicates that the object is a person or group who is especially well-known or significant as a victim of 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_69a4939e889c8190ac148b3ac1a7f90b |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b3bcad2481908b83575b2fb80d14 |
completed | March 1, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69a4b28ff5948190982c4439eadf9d87 |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:39 p.m.