Triple
T13913391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amon |
E334553
|
entity |
| Predicate | idolatryPractices |
P112262
|
FINISHED |
| Object | worship of foreign gods |
—
|
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: worship of foreign gods | Statement: [Amon, idolatryPractices, worship of foreign gods]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: idolatryPractices Context triple: [Amon, idolatryPractices, worship of foreign gods]
-
A.
worshippedIn
Indicates that a particular deity, figure, or object of reverence is the focus of religious or spiritual worship within a specified place or context.
-
B.
idolsBelievedToBe
Indicates that certain idols are regarded or considered to possess a particular nature, identity, or attribute.
-
C.
ritualCategory
Indicates the classification relationship that assigns a ritual to a specific ritual type or category.
-
D.
practicesReligion
Indicates that an entity actively follows, observes, or participates in the beliefs, rituals, and customs of a particular religion.
-
E.
worshipsDeity
Indicates that one entity reveres, honors, or performs religious devotion toward another entity regarded as a deity.
- 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_69d81c5eaa9c819083b1ff8689179565 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de27245c648190b2946845ce0fdbf8 |
completed | April 14, 2026, 11:38 a.m. |
| PD | Predicate disambiguation | batch_69de059e4ba881908554f72e889719fa |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de239524688190a0f2408c239cfcaa |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 9, 2026, 10:16 p.m.