Triple
T158294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paschal candle |
E3225
|
entity |
| Predicate | incenseGrainsSymbolize |
P129
|
FINISHED |
| Object | five wounds of Christ |
—
|
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: five wounds of Christ | Statement: [Paschal candle, incenseGrainsSymbolize, five wounds of Christ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: incenseGrainsSymbolize Context triple: [Paschal candle, incenseGrainsSymbolize, five wounds of Christ]
-
A.
symbolizes
chosen
Indicates that one entity stands for, represents, or is used as a sign for another entity, concept, or idea.
-
B.
enshrines
Indicates that one entity formally preserves, protects, or honors another by giving it a permanent, often sacred or legally recognized, status.
-
C.
hasRitual
Indicates that an entity performs, observes, or is associated with a specific ritual or ceremonial practice.
-
D.
starSign
Indicates the astrological zodiac sign associated with a person or entity based on their birth date.
-
E.
worshippedIn
Indicates that a particular deity, figure, or object of reverence is the focus of religious or spiritual worship within a specified place or context.
- 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_69a2527757ec819090b8becb2cf1a862 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a2583169a0819081b658882e5bc452 |
completed | Feb. 28, 2026, 2:51 a.m. |
| PD | Predicate disambiguation | batch_69a2565f30848190a2a71fdb7dc140b5 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.