Triple
T5050761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mahadevi |
E113778
|
entity |
| Predicate | alsoKnownAs |
P39
|
FINISHED |
| Object | Devi |
E20132
|
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: Devi | Statement: [Mahadevi, alsoKnownAs, Devi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Devi Context triple: [Mahadevi, alsoKnownAs, Devi]
-
A.
Devi
chosen
Devi is the supreme goddess in Hinduism, embodying the divine feminine power (Shakti) in its many forms such as Durga, Parvati, Lakshmi, and Saraswati.
-
B.
Bhudevi
Bhudevi is the Hindu earth goddess and consort of Lord Vishnu, revered as the personification of the fertile, nurturing aspects of the Earth.
-
C.
Māyādevī
Māyādevī is revered in Buddhist tradition as the queen and mother of Siddhartha Gautama, who became the Buddha.
-
D.
Devasena
Devasena is a Hindu goddess known as one of the wives of the war god Kartikeya, often associated with valor and divine grace.
-
E.
Deva
Deva is the Roman-era name for the ancient fortress and settlement that later became the modern English city of Chester.
- 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_69bd44391fc48190a311ce9c826c209b |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7425df74819091cfde348dd16a68 |
completed | March 20, 2026, 4:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf28f6f5148190ac40ba3256f8264b |
completed | March 21, 2026, 11:25 p.m. |
Created at: March 20, 2026, 1:37 p.m.