Triple

T4515541
Position Surface form Disambiguated ID Type / Status
Subject Pandavas E102144 entity
Predicate member P10 FINISHED
Object Nakula E115661 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: Nakula | Statement: [Pandavas, member, Nakula]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Nakula
Context triple: [Pandavas, member, Nakula]
  • A. Nakula chosen
    Nakula is a heroic prince in the Indian epic Mahabharata, renowned as one of the five Pandava brothers and celebrated for his exceptional skill in swordsmanship and horse-keeping.
  • B. Bhima
    Bhima is a major river in western India that flows through the states of Maharashtra, Karnataka, and Telangana before joining the Krishna River.
  • C. Bhima
    Bhima is a powerful warrior prince from the Indian epic Mahabharata, renowned for his immense strength, loyalty, and pivotal role among the Pandava brothers.
  • D. Sahadeva
    Sahadeva is one of the five Pandava brothers in the Indian epic Mahabharata, renowned for his wisdom, knowledge of astrology, and loyalty.
  • E. Karna
    Karna is a legendary warrior and tragic hero of the Indian epic Mahabharata, renowned for his unmatched archery skills, unwavering loyalty, and complex moral dilemmas.
  • 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_69bd43d6251c81909deecce3e6e9d69c completed March 20, 2026, 12:55 p.m.
NER Named-entity recognition batch_69bd5725745c81908bb462ba9537ae14 completed March 20, 2026, 2:18 p.m.
NED1 Entity disambiguation (via context triple) batch_69bd7f8f66ac8190b719a653686c7258 completed March 20, 2026, 5:10 p.m.
Created at: March 20, 2026, 1:02 p.m.