Triple
T19595834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neang Seda |
E470345
|
entity |
| Predicate | basedOn |
P98
|
FINISHED |
| Object | Sita |
—
|
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: Sita | Statement: [Neang Seda, basedOn, Sita]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sita Context triple: [Neang Seda, basedOn, Sita]
-
A.
Sita
chosen
Sita is a revered heroine in Hindu mythology, celebrated as the devoted wife of Lord Rama and an enduring symbol of virtue, loyalty, and courage.
-
B.
Urmila
Urmila is a character in the Hindu epic Ramayana, revered as the devoted wife of Lakshmana and sister of Sita.
-
C.
Shikhandi
Shikhandi is a pivotal and complex warrior in the Mahabharata, known for being instrumental in the downfall of Bhishma during the Kurukshetra War due to their unique gender history and past-life connection.
-
D.
Sita Kund
Sita Kund is a revered Hindu pilgrimage spot in Panchavati, Nashik, associated with the epic Ramayana and worship of Sita.
-
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_69d8e510024481908415c0d616fa6186 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e6407a09608190aa1df92f8c21f9e7 |
completed | April 20, 2026, 3:04 p.m. |
Created at: April 10, 2026, 1:43 p.m.