Triple
T941890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ganesha |
E20323
|
entity |
| Predicate | consort |
P13
|
FINISHED |
| Object | Siddhi |
E126260
|
NE 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: Siddhi | Statement: [Ganesha, consort, Siddhi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Siddhi Context triple: [Ganesha, consort, Siddhi]
-
A.
Riddhi
chosen
Riddhi is a Hindu goddess associated with prosperity and good fortune, traditionally regarded as one of the consorts of Lord Ganesha.
-
B.
Chitrangada
Chitrangada is a warrior princess from the Indian epic Mahabharata, known as one of Arjuna’s wives and the daughter of the king of Manipur.
-
C.
Savyasachi
Savyasachi is a celebrated epithet of the Mahabharata hero Arjuna, highlighting his legendary ambidextrous skill in archery and combat.
-
D.
Pranhita
Pranhita is a major river in central India that flows through the states of Maharashtra and Telangana before joining the Godavari River.
-
E.
Shipra
Shipra is a sacred river in the Indian state of Madhya Pradesh, especially revered in Ujjain as a major Hindu pilgrimage site.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69a493b0270c81909e6c9ce310f6aa55 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b3a1a4888190997adf56eb761431 |
completed | March 1, 2026, 9:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ac7631d5d081909c1229d1b792ddb6 |
completed | March 7, 2026, 7:02 p.m. |
Created at: March 1, 2026, 7:40 p.m.