Triple
T1363298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Magi |
E29144
|
entity |
| Predicate | symbolismOfMyrrh |
P129
|
FINISHED |
| Object | suffering and death of Jesus |
—
|
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: suffering and death of Jesus | Statement: [Magi, symbolismOfMyrrh, suffering and death of Jesus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: symbolismOfMyrrh Context triple: [Magi, symbolismOfMyrrh, suffering and death of Jesus]
-
A.
symbolizes
chosen
Indicates that one entity stands for, represents, or is used as a sign for another entity, concept, or idea.
-
B.
hasSacredSymbol
Indicates that one entity serves as a sacred or religiously significant symbol associated with another entity.
-
C.
significanceInTheology
Indicates the importance or influence that something holds within theological beliefs, doctrines, or religious thought.
-
D.
signOfCovenant
Indicates that something serves as a visible or symbolic marker confirming the existence and terms of a covenant between parties.
-
E.
sacramentOfHealing
Indicates a relationship in which a religious sacrament is administered to bring spiritual or physical healing to a person.
- 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_69a498d77abc8190913bf57e5f51d2c4 |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c2b5d05c81908b49e282648e073a |
completed | March 1, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69a4bef945c08190a027472fdd695ea5 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:57 p.m.