Triple
T19082940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Altar of Incense |
E467073
|
entity |
| Predicate | atonementRite |
P26551
|
FINISHED |
| Object | blood applied to its horns |
—
|
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: blood applied to its horns | Statement: [Altar of Incense, atonementRite, blood applied to its horns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: atonementRite Context triple: [Altar of Incense, atonementRite, blood applied to its horns]
-
A.
ordinationRite
Indicates the formal religious ceremony or ritual through which a person is conferred an office or ordained to a specific role.
-
B.
atonementModel
Indicates the specific theological framework or theory that explains how atonement (reconciliation between parties, often God and humans) is understood to occur.
-
C.
usesRitually
Indicates that an entity employs or performs something as part of a ritual or ceremonial practice.
-
D.
partOfRitual
chosen
Indicates that an action, object, or event is included as a component or step within a larger ritual.
-
E.
notableRite
Indicates that an entity is associated with a significant or distinguished ritual, ceremony, or formal rite.
- 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_69d8dd04f4488190b1121cc53ef2bfd6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e2eab58c8190a987c88d633c92ec |
completed | April 20, 2026, 8:25 a.m. |
| PD | Predicate disambiguation | batch_69e4b9a604308190a3235184f9f2c056 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:04 p.m.