Triple
T33241643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint Maurice of Magdeburg |
E850976
|
entity |
| Predicate | typeOfMartyr |
P165594
|
FINISHED |
| Object | Christian martyr |
—
|
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: Christian martyr | Statement: [Saint Maurice of Magdeburg, typeOfMartyr, Christian martyr]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfMartyr Context triple: [Saint Maurice of Magdeburg, typeOfMartyr, Christian martyr]
-
A.
martyrType
chosen
Indicates that one entity is classified as a specific type or category of martyr in relation to another entity.
-
B.
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.
-
C.
reasonForMartyrdom
Indicates the cause, motive, or circumstances that led to an individual’s martyrdom.
-
D.
martyrGroup
Indicates that a group is characterized by or associated with individuals who have died or sacrificed themselves for a cause, often being honored or recognized as martyrs.
-
E.
martyrAssociated
Indicates that there is a relationship of connection or involvement between an entity and a martyr, such as affiliation, support, or commemoration.
- 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_69f34962386c81909ddc3bf9e18ddeb8 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a00a74c0564819081e1c4c29b9d0d15 |
completed | May 10, 2026, 3:42 p.m. |
| PD | Predicate disambiguation | batch_6a00a6a63ef48190a743c88534d9d672 |
completed | May 10, 2026, 3:39 p.m. |
Created at: May 1, 2026, 1:31 a.m.