Triple
T26595326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qarin |
E667474
|
entity |
| Predicate | requiresSacrificialAnimal |
P181298
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Qarin, requiresSacrificialAnimal, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresSacrificialAnimal Context triple: [Qarin, requiresSacrificialAnimal, yes]
-
A.
sacrificedAnimal
Indicates that one entity killed or offered an animal as a sacrifice, typically for a ritual, religious, or ceremonial purpose, in relation to another entity or context.
-
B.
sacrificeAnimalType
Indicates that an entity performs or is involved in the act of sacrificing an animal of a specified type.
-
C.
sacrificedAnimalsAt
Indicates that an entity performed or conducted animal sacrifices at a specific location or site.
-
D.
sacrificialMedium
Indicates that one entity serves as the medium or vehicle through which another entity is sacrificed or offered.
-
E.
methodOfSacrifice
Indicates the specific way or procedure by which a sacrifice is carried out.
- F. None of above. chosen
Provenance (4 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_69ee9cfc385081909ac9ae178030a06e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f7688dd3d08190ad13d0e780570a1c |
completed | May 3, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69f767fcf2f881908bacc7bfc38e68a5 |
completed | May 3, 2026, 3:21 p.m. |
| PDg | Predicate description generation | batch_69f7688cea58819098bdfd7c80df7634 |
completed | May 3, 2026, 3:23 p.m. |
Created at: April 27, 2026, 2:10 a.m.