Triple
T25525065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vaikasi Visakam |
E639751
|
entity |
| Predicate | relatedDeityFamily |
P190470
|
FINISHED |
| Object | son of Shiva and Parvati |
—
|
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: son of Shiva and Parvati | Statement: [Vaikasi Visakam, relatedDeityFamily, son of Shiva and Parvati]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedDeityFamily Context triple: [Vaikasi Visakam, relatedDeityFamily, son of Shiva and Parvati]
-
A.
associatedReligiousFamily
Indicates a relationship where an entity is linked or connected to a particular religious family or tradition.
-
B.
hasSiblingDeity
Indicates that one deity is a sibling (sharing at least one parent) of another deity.
-
C.
relatedDeityResidence
Indicates that a deity is associated with, dwells in, or is traditionally believed to reside in a particular place or realm.
-
D.
relatedNameOfGod
Indicates that one entity is a name, title, or designation that refers to or is associated with God.
-
E.
sharesDeitiesWith
Indicates that two entities have one or more deities in common within their respective religious or mythological systems.
- 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_69e75dbf3f9c8190b3f2a75d1b75d127 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69fcc7779d248190afdb348a95375443 |
completed | May 7, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
| PDg | Predicate description generation | batch_69fcc73264e08190b0b5917f32226fae |
completed | May 7, 2026, 5:09 p.m. |
Created at: April 21, 2026, 3:09 p.m.