Triple
T10786150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Janaka |
E254456
|
entity |
| Predicate | name |
P16
|
FINISHED |
| Object | Janaka |
E254456
|
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: Janaka | Statement: [King Janaka, name, Janaka]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Janaka Context triple: [King Janaka, name, Janaka]
-
A.
King Janaka
chosen
King Janaka is a revered philosopher-king in ancient Indian tradition, best known as the wise ruler of Videha and the father of Sita in the Ramayana.
-
B.
Drupada
Drupada is a king in the Indian epic Mahabharata, best known as the ruler of Panchala and the father of Draupadi and Dhrishtadyumna.
-
C.
पाण्डु
पाण्डु महाभारत के अनुसार हस्तिनापुर के राजा और पांडवों के पिता के रूप में प्रसिद्ध पौराणिक चरित्र हैं।
-
D.
King Shantanu
King Shantanu is a legendary monarch of the Kuru dynasty in the Indian epic Mahabharata, best known as the father of Bhishma and a key ancestor of the Pandavas and Kauravas.
-
E.
Pradyumna
Pradyumna is a prominent figure in Hindu mythology, known as the son of Krishna and Rukmini and considered an incarnation of the love god Kamadeva.
- 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_69d6aa609f008190a294200aefcb7bd5 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d732d44b488190a9f3ab9b177e737a |
completed | April 9, 2026, 5:02 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69dff7b050ec8190b75877d5724c2aec |
completed | April 15, 2026, 8:40 p.m. |
Created at: April 8, 2026, 9:17 p.m.