Triple
T22198598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lion of the Covenant |
E548612
|
entity |
| Predicate | associatedWithCauseOfDeath |
P144
|
FINISHED |
| Object | martyrdom |
—
|
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: martyrdom | Statement: [Lion of the Covenant, associatedWithCauseOfDeath, martyrdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithCauseOfDeath Context triple: [Lion of the Covenant, associatedWithCauseOfDeath, martyrdom]
-
A.
causeOfDeath
chosen
Indicates the specific factor, event, or condition that directly resulted in an entity’s death.
-
B.
associatedWithDeathOf
Indicates a relationship where one entity is connected in some relevant way to the death of another entity, such as by involvement, causation, or contextual association.
-
C.
reasonForDeath
Indicates the cause, circumstance, or condition that led to an entity’s death.
-
D.
namedAfterCauseOfDeath
Indicates that an entity is named after the cause of death of a person or organism.
-
E.
deathCauseUncertainty
Indicates that there is ambiguity, doubt, or lack of definitive information about the cause of death in the relationship being described.
- 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_69e11e3ecc7c8190b5f94cd8f42e9d37 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12ae98808819081582a57bca6312b |
completed | April 28, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69e71b48576c8190a8e93738fd9cfda5 |
completed | April 21, 2026, 6:38 a.m. |
Created at: April 16, 2026, 8:36 p.m.