Triple
T19410129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kandha tribal communities |
E485564
|
entity |
| Predicate | traditionalDeities |
P85058
|
FINISHED |
| Object | village deities |
—
|
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: village deities | Statement: [Kandha tribal communities, traditionalDeities, village deities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalDeities Context triple: [Kandha tribal communities, traditionalDeities, village deities]
-
A.
otherDeity
Indicates that one deity is distinct from and not identical to another deity within a given context or system.
-
B.
deityCategory
chosen
Indicates that one entity is classified as belonging to a particular category or type of deity in relation to another entity.
-
C.
guardianDeitiesOrFigures
Indicates a protective or watchful relationship in which certain deities or figures serve as guardians over specific people, places, objects, or domains.
-
D.
sharesDeitiesWith
Indicates that two entities have one or more deities in common within their respective religious or mythological systems.
-
E.
worshippedDeityCulture
Indicates that a particular culture reveres, honors, or practices religious devotion toward a specific 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_69d8e8d5162481909db12435d9535c1a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e62af4cc0c81909056b5e2ee574ab1 |
completed | April 20, 2026, 1:32 p.m. |
| PD | Predicate disambiguation | batch_69e4fd68b1f881908d273de1fee81a75 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:37 p.m.