Triple

T19821533
Position Surface form Disambiguated ID Type / Status
Subject Mahishasura E476205 entity
Predicate associatedPlace P1481 FINISHED
Object Mysore 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: Mysore | Statement: [Mahishasura, associatedPlace, Mysore]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mysore
Context triple: [Mahishasura, associatedPlace, Mysore]
  • A. Mysuru chosen
    Mysuru is a historic city in the southern Indian state of Karnataka, renowned for its royal heritage, palaces, and cultural festivals such as Dasara.
  • B. Belgaum
    Belgaum is a major city in the Indian state of Karnataka, known as an important commercial, industrial, and military hub near the Maharashtra–Goa border.
  • C. Mangalore
    Mangalore is a major port city on the southwestern coast of India, known for its maritime trade, diverse culture, and role as a commercial hub of Karnataka.
  • D. Madikeri
    Madikeri is a scenic hill town in Karnataka’s Coorg region, known for its cool climate, coffee plantations, and lush Western Ghats landscapes.
  • E. Vijayapura
    Vijayapura is a historic city in the Indian state of Karnataka, renowned for its rich Deccan-era architecture and monuments such as the Gol Gumbaz.
  • 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_69d8e51c7c188190b926f3a2a7b5f881 completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e654fee3e48190ae728e49748ad268 completed April 20, 2026, 4:31 p.m.
Created at: April 10, 2026, 1:50 p.m.