Triple
T18324310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vidyavati Kaur |
E438963
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Vidyavati |
—
|
NE NERFINISHED |
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: Vidyavati | Statement: [Vidyavati Kaur, givenName, Vidyavati]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vidyavati Context triple: [Vidyavati Kaur, givenName, Vidyavati]
-
A.
Vidyavati
chosen
Vidyavati is an Indian woman whose given name is associated with the full name Vidyavati Kaur.
-
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.
Bhagyavati
Bhagyavati was a royal woman of the Western Chalukya dynasty, known primarily as the mother of the notable ruler Tailapa II.
-
D.
Lalita Tripurasundari
Lalita Tripurasundari is a principal Hindu goddess of the Sri Vidya tradition, revered as the supremely beautiful and benevolent form of the Divine Mother who governs creation, preservation, and dissolution.
-
E.
Rukmini
Rukmini is a principal queen of the Hindu god Krishna, revered as an incarnation of the goddess Lakshmi and celebrated for her devotion and role in Krishna’s life.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8b916a2d081909e249e4902f6aad9 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e50aa93fb0819083293b80e8400c4e |
completed | April 19, 2026, 5:02 p.m. |
Created at: April 10, 2026, 10:36 a.m.