Triple
T19026103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Astika sub-parva |
E465613
|
entity |
| Predicate | hasMainCharacter |
P1183
|
FINISHED |
| Object | Vasuki |
—
|
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: Vasuki | Statement: [Astika sub-parva, hasMainCharacter, Vasuki]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vasuki Context triple: [Astika sub-parva, hasMainCharacter, Vasuki]
-
A.
Vasuki
chosen
Vasuki is the mighty serpent king in Hindu mythology, often depicted as a naga who plays a central role in the churning of the ocean (Samudra Manthan).
-
B.
Thasra
Thasra is a town located in the Kheda district of the Indian state of Gujarat.
-
C.
Vitashoka
Vitashoka was a lesser-known son of the Mauryan emperor Bindusara and brother of the famous Indian emperor Ashoka.
-
D.
Mitra-Varuna
Mitra-Varuna is a dual Vedic deity pair embodying complementary aspects of cosmic order, social contracts, and sovereign authority in early Indo-Aryan religion.
-
E.
Yaudheya
Yaudheya is a relatively lesser-known figure in the Mahabharata tradition, remembered primarily as a son of the Pandava king Yudhishthira.
- 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_69d8dd025c188190a1d81f5b4ec7e2c6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d73cace0819096bdac6dc8c17253 |
completed | April 20, 2026, 7:35 a.m. |
Created at: April 10, 2026, 12:02 p.m.