Triple
T4930769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ganapatya tradition |
E110688
|
entity |
| Predicate | recognizesOtherDeitiesAs |
P20263
|
FINISHED |
| Object | subordinate to Ganesha |
—
|
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: subordinate to Ganesha | Statement: [Ganapatya tradition, recognizesOtherDeitiesAs, subordinate to Ganesha]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recognizesOtherDeitiesAs Context triple: [Ganapatya tradition, recognizesOtherDeitiesAs, subordinate to Ganesha]
-
A.
otherDeity
Indicates that one deity is distinct from and not identical to another deity within a given context or system.
-
B.
viewOnOtherDeities
chosen
Indicates how one deity regards, evaluates, or conceptually relates to other deities.
-
C.
sharesDeitiesWith
Indicates that two entities have one or more deities in common within their respective religious or mythological systems.
-
D.
typeOfDeity
Indicates that one entity is classified as a specific kind or category of deity in relation to another.
-
E.
worshippedAlongside
Indicates that two deities or sacred figures were venerated together within the same religious context, ritual, or cult practice.
- 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_69bd4415190c8190817bee7ec9f9f944 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd706245e48190a61d573438461c30 |
completed | March 20, 2026, 4:05 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3695c8819094e7ad2f6d4ba1ac |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:30 p.m.