Triple
T22019790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shani Shingnapur |
E543810
|
entity |
| Predicate | hasMainDeityForm |
P86454
|
FINISHED |
| Object | stone slab representing Shani |
—
|
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: stone slab representing Shani | Statement: [Shani Shingnapur, hasMainDeityForm, stone slab representing Shani]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainDeityForm Context triple: [Shani Shingnapur, hasMainDeityForm, stone slab representing Shani]
-
A.
mainDeityForm
chosen
Indicates that one entity is the primary or canonical divine form or manifestation of another deity.
-
B.
mainDeity
Indicates that one entity serves as the primary or chief deity worshiped, revered, or associated with another entity (such as a religion, temple, or culture).
-
C.
hasDeity
Indicates that one entity recognizes, worships, or is associated with another entity as its deity or divine figure.
-
D.
hasConsortDeityForm
Indicates that an entity has a consort specifically in their deity or divine form.
-
E.
hasConsortDeity
Indicates that one deity is the consort (spouse or intimate divine partner) of another deity.
- 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_69e11e2e8ea4819084210fe06d3a1b8d |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f127c6b5fc8190bc49ddb058f28a44 |
completed | April 28, 2026, 9:33 p.m. |
| PD | Predicate disambiguation | batch_69e6f62dc9d88190ae387f145f9528de |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:23 p.m.