Triple
T10128037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint Panteleimon |
E226263
|
entity |
| Predicate | martyrdomMethod |
P92138
|
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: [Saint Panteleimon, martyrdomMethod, beheading]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: martyrdomMethod Context triple: [Saint Panteleimon, martyrdomMethod, beheading]
-
A.
martyr
Indicates that an entity is killed or suffers greatly, typically for a belief, cause, or principle, often being regarded or treated as a martyr as a result.
-
B.
martyrdomStatus
Indicates the state or condition of an entity with respect to being recognized or regarded as a martyr.
-
C.
martyredUnder
Indicates that an entity was killed or executed as a martyr during the rule, authority, or actions of another entity.
-
D.
martyrdomContext
Indicates the circumstances or situational factors under which an entity becomes a martyr or is regarded as having undergone martyrdom.
-
E.
traditionallyMartyredWith
Indicates that an entity is customarily believed or depicted to have been martyred using a particular method, instrument, or circumstance.
- F. None of above. chosen
Provenance (4 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_69ca843057b48190a86730167f5d6b98 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cdd2f0a0e881909267a83fbeb31f0c |
completed | April 2, 2026, 2:22 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba1d360819087698d04a53cc87e |
completed | April 1, 2026, 4:45 p.m. |
| PDg | Predicate description generation | batch_69cd4fed19d481909d2c7ff1114664b6 |
completed | April 1, 2026, 5:03 p.m. |
Created at: March 30, 2026, 9:05 p.m.