Triple
T36301403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hårga cult |
E893822
|
entity |
| Predicate | sacrificialCustom |
P36512
|
FINISHED |
| Object | elderly members sacrifice themselves at age 72 |
—
|
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: elderly members sacrifice themselves at age 72 | Statement: [Hårga cult, sacrificialCustom, elderly members sacrifice themselves at age 72]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sacrificialCustom Context triple: [Hårga cult, sacrificialCustom, elderly members sacrifice themselves at age 72]
-
A.
sacrificialMedium
Indicates that one entity serves as the medium or vehicle through which another entity is sacrificed or offered.
-
B.
sacrificeType
chosen
Indicates the specific kind or category of sacrifice involved in a sacrificial action or relationship.
-
C.
sacrifice
Indicates giving up something of value, often for the benefit, protection, or advantage of another entity or goal.
-
D.
sacrificedTo
Indicates that one entity is offered or given up as a sacrifice in honor of, or to appease, another entity.
-
E.
sacrificeAcceptedBy
Indicates that a sacrificial offering made by one entity is received and deemed acceptable by another entity.
- 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_69f76e4c1b248190b10667d0213537fe |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7ba6d06f48190a71b5a2f19e2232f |
completed | May 3, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a4aad48190a62e41c5e39339d9 |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:09 p.m.