Triple
T20402844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Supay |
E500379
|
entity |
| Predicate | propitiatedBy |
P41622
|
FINISHED |
| Object | offerings |
—
|
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: offerings | Statement: [Supay, propitiatedBy, offerings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: propitiatedBy Context triple: [Supay, propitiatedBy, offerings]
-
A.
wasPacifiedBy
Indicates that an entity became calm, subdued, or brought under control as a result of the actions or influence of another entity.
-
B.
relievedBy
Indicates that one entity eases, reduces, or removes the burden, pain, stress, or responsibility experienced by another entity.
-
C.
bribedBy
Indicates that an entity has received a bribe from another entity, implying an exchange of value to influence the entity’s actions or decisions.
-
D.
sacrificeAcceptedBy
chosen
Indicates that a sacrificial offering made by one entity is received and deemed acceptable by another entity.
-
E.
blessedBy
Indicates that one entity has conferred a blessing, favor, or sacred endorsement upon 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_69e0b4a81bec8190b69adfdc1336a015 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6798fc3b88190a372c34102bfaa6f |
completed | April 20, 2026, 7:07 p.m. |
| PD | Predicate disambiguation | batch_69e5765d7cb48190adec18d6d1e3d263 |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:29 a.m.