Triple
T22186245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Epulones |
E548303
|
entity |
| Predicate | usedRitualObjects |
P7123
|
FINISHED |
| Object | sacrificial meat portions |
—
|
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: sacrificial meat portions | Statement: [Epulones, usedRitualObjects, sacrificial meat portions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedRitualObjects Context triple: [Epulones, usedRitualObjects, sacrificial meat portions]
-
A.
hasRitualObjectMaterial
Indicates that a ritual object is made from, composed of, or primarily constructed using a specified material.
-
B.
hasRitualObject
chosen
Indicates that an entity possesses, uses, or is associated with an object specifically employed in a ritual or ceremonial context.
-
C.
usesRitually
Indicates that an entity employs or performs something as part of a ritual or ceremonial practice.
-
D.
hasRitualElements
Indicates that one entity incorporates, contains, or is characterized by ritualistic components, practices, or features associated with formalized ceremonies or rites.
-
E.
appearsInRitual
Indicates that an entity is included, featured, or participates as a component or element within a specific ritual.
- 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_69e11e3e0c7c8190b30d278845e2497e |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12aa8f178819094d1556df5aee5b9 |
completed | April 28, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69e71b48576c8190a8e93738fd9cfda5 |
completed | April 21, 2026, 6:38 a.m. |
Created at: April 16, 2026, 8:35 p.m.