Triple
T28797353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Two Ewalds |
E727123
|
entity |
| Predicate | martyrType |
P165594
|
FINISHED |
| Object | missionary martyrs |
—
|
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: missionary martyrs | Statement: [The Two Ewalds, martyrType, missionary martyrs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: martyrType Context triple: [The Two Ewalds, martyrType, missionary martyrs]
-
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.
martyrAssociated
Indicates that there is a relationship of connection or involvement between an entity and a martyr, such as affiliation, support, or commemoration.
-
C.
martyrdomMethod
Indicates the method or means by which an individual becomes a martyr (i.e., how the martyrdom is carried out).
-
D.
martyrdomStatus
Indicates the state or condition of an entity with respect to being recognized or regarded as a martyr.
-
E.
martyrTitle
Indicates that an entity holds the title or designation of a martyr, typically recognizing death or suffering for a cause, belief, or principle.
- 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_69f0319b7c44819085736bcc256185e6 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6596b210481908af6cd555748f75b |
completed | May 2, 2026, 8:07 p.m. |
| PD | Predicate disambiguation | batch_69f65760fd3081908ffe014a5e2bf069 |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f658ebeca4819096beb3f98f73fe31 |
completed | May 2, 2026, 8:05 p.m. |
Created at: April 28, 2026, 6:25 a.m.