Triple
T36887887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Decii Mures |
E911658
|
entity |
| Predicate | sacrificialAct |
P36512
|
FINISHED |
| Object | ritual battlefield self‑devotion to the gods |
—
|
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: ritual battlefield self‑devotion to the gods | Statement: [Decii Mures, sacrificialAct, ritual battlefield self‑devotion to the gods]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sacrificialAct Context triple: [Decii Mures, sacrificialAct, ritual battlefield self‑devotion to the gods]
-
A.
sacrifice
Indicates giving up something of value, often for the benefit, protection, or advantage of another entity or goal.
-
B.
sacrificeType
chosen
Indicates the specific kind or category of sacrifice involved in a sacrificial action or relationship.
-
C.
resultOfSacrifice
Indicates that something exists or occurs as the outcome or consequence of a sacrificial act.
-
D.
sacrificedBy
Indicates that an entity has been given up, killed, or offered as a sacrifice by another entity.
-
E.
sacrificialMedium
Indicates that one entity serves as the medium or vehicle through which another entity is sacrificed or offered.
- 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_69f76e8335908190b77e7e11d0e80820 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb554c35c8819093fa5aa226d81971 |
completed | May 6, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f7cf79ddb08190a083405cccc14137 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:13 p.m.