Triple
T13729160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shillem |
E329745
|
entity |
| Predicate | worshippedAsDeity |
P8132
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [Shillem, worshippedAsDeity, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worshippedAsDeity Context triple: [Shillem, worshippedAsDeity, no]
-
A.
worshipedAs
Indicates that one entity regards and treats another as a deity or sacred figure, offering reverence, devotion, or religious honor.
-
B.
worshippedAs
chosen
Indicates that one entity is regarded and treated with religious reverence or devotion by another entity.
-
C.
honorsDeityAs
Indicates that one entity venerates, worships, or regards another entity as a particular deity or divine figure.
-
D.
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.
-
E.
hasDeity
Indicates that one entity recognizes, worships, or is associated with another entity as its deity or divine figure.
- 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_69d80772315881908f980cae40d91664 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69de01f746cc8190abde237bbb7e6c78 |
completed | April 14, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69dbbe92d77c81908e0244cffb7f78c5 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:55 p.m.