Triple

T7386233
Position Surface form Disambiguated ID Type / Status
Subject Anglo-Mysore Wars E170386 entity
Predicate location P40 FINISHED
Object Mysore E80753 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: Mysore | Statement: [Anglo-Mysore Wars, location, Mysore]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mysore
Context triple: [Anglo-Mysore Wars, location, 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. 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.
  • C. Madikeri
    Madikeri is a scenic hill town in Karnataka’s Coorg region, known for its cool climate, coffee plantations, and lush Western Ghats landscapes.
  • D. Bidar
    Bidar is a historic city in the Indian state of Karnataka, renowned for its medieval fort, rich Deccan Sultanate heritage, and distinctive Bidri metalwork.
  • E. Shivamogga
    Shivamogga is a city in the Malnad region of Karnataka, India, known for its scenic landscapes, proximity to waterfalls like Jog Falls, and role as a regional commercial and educational hub.
  • 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_69c68a5e2c9081909e713ce866e0060a completed March 27, 2026, 1:47 p.m.
NER Named-entity recognition batch_69c6f1f117ec8190a97cbd0b35d5811a completed March 27, 2026, 9:09 p.m.
NED1 Entity disambiguation (via context triple) batch_69c810e879e88190a421409194868587 completed March 28, 2026, 5:33 p.m.
Created at: March 27, 2026, 3:08 p.m.