Triple

T5178707
Position Surface form Disambiguated ID Type / Status
Subject Babruvahana E116862 entity
Predicate raisedIn P7868 FINISHED
Object Manipura E500119 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: Manipura | Statement: [Babruvahana, raisedIn, Manipura]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Manipura
Context triple: [Babruvahana, raisedIn, Manipura]
  • A. Manipura chosen
    Manipura is an ancient kingdom in the Indian epic Mahabharata, known as the realm ruled by Babruvahana, the son of Arjuna.
  • B. Indrapura
    Indrapura was a prominent historical capital city of the Champa kingdom in what is now central Vietnam.
  • C. Kishkindha
    Kishkindha is the mythical monkey kingdom ruled by Sugriva in the Indian epic Ramayana, where Rama forms an alliance with the vanara army to search for Sita.
  • D. Shambhala
    Shambhala is a renowned steel roller coaster at PortAventura Park in Spain, celebrated for its towering height, high speeds, and status as one of Europe’s premier hypercoasters.
  • E. Madra
    Madra was an ancient kingdom in the northwest of the Indian subcontinent, frequently mentioned in the Mahabharata and associated with figures like King Shalya and the Pandava prince Nakula.
  • 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_69bd446140f08190becb93c61158f27f completed March 20, 2026, 12:58 p.m.
NER Named-entity recognition batch_69bd7976339481909ece900de22064f2 completed March 20, 2026, 4:44 p.m.
NED1 Entity disambiguation (via context triple) batch_69bee07d20208190a423a9a395ac9d32 completed March 21, 2026, 6:16 p.m.
Created at: March 20, 2026, 1:45 p.m.