Triple

T17096500
Position Surface form Disambiguated ID Type / Status
Subject Mahabharata tradition in Java E414863 entity
Predicate featuresCharacter P626 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: [Mahabharata tradition in Java, featuresCharacter, Janaka]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Janaka
Context triple: [Mahabharata tradition in Java, featuresCharacter, 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_69d886cfc8e88190b05ba466edd35591 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3dbfdc9c88190b4e75bbdf4105c1e completed April 18, 2026, 7:31 p.m.
NED1 Entity disambiguation (via context triple) batch_6a012eedfd7c8190b267dedd403f5f2b completed May 11, 2026, 1:20 a.m.
Created at: April 10, 2026, 5:35 a.m.