Triple
T8798870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kitchen God |
E209350
|
entity |
| Predicate | aimOfOfferings |
P36122
|
FINISHED |
| Object | to secure a favorable report |
—
|
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: to secure a favorable report | Statement: [Kitchen God, aimOfOfferings, to secure a favorable report]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aimOfOfferings Context triple: [Kitchen God, aimOfOfferings, to secure a favorable report]
-
A.
aimOf
Indicates that one entity serves as the goal, purpose, or intended target of another entity’s action, plan, or existence.
-
B.
isOftenOfferedToDeity
Indicates that something is frequently presented or dedicated as an offering to a deity.
-
C.
aimsToProvide
Indicates that one entity intends or is designed to supply, deliver, or make available something to another entity.
-
D.
offering
Indicates that one entity presents or provides something to another entity, typically as a gift, contribution, or proposal.
-
E.
ritualPurpose
chosen
Indicates the intended function, goal, or role that a ritual is meant to serve or fulfill.
- 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_69ca836240888190a62b262e56a69d2f |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5fb7491c8190bcdb98d6cc003d9e |
completed | March 31, 2026, 11:58 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1d48f08190b325a77d4c76d223 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:44 p.m.