Triple

T20965349
Position Surface form Disambiguated ID Type / Status
Subject Satanika E516351 entity
Predicate grandfather P979 FINISHED
Object Pandu 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: Pandu | Statement: [Satanika, grandfather, Pandu]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Pandu
Context triple: [Satanika, grandfather, Pandu]
  • A. Pandu chosen
    Pandu is a key figure in the Indian epic Mahabharata, the Kuru king and father of the Pandavas.
  • B. Sanjaya
    Sanjaya was an early Javanese king traditionally regarded as the founder of the Mataram (Medang) Kingdom and the Sanjaya dynasty in Central Java.
  • C. Sanjaya
    Sanjaya is the charioteer and seer in the Mahabharata who, granted divine vision, narrates the events of the Kurukshetra war to the blind king Dhritarashtra.
  • D. Suryaputra
    Suryaputra is an epithet of the legendary warrior Karna from the Indian epic Mahabharata, highlighting his divine parentage as the son of the sun god Surya.
  • E. Pangeran Puger
    Pangeran Puger was a Javanese prince of the Mataram Sultanate who later became Susuhunan Pakubuwono I, a key ruler in Central Java’s dynastic and political struggles in the late 17th and early 18th centuries.
  • 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_69e0b4fde6c48190af1398e7e734629e completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6fb72ef4c8190bebdd2cef3c2148c completed April 21, 2026, 4:22 a.m.
Created at: April 16, 2026, 1:32 p.m.