Triple

T11181587
Position Surface form Disambiguated ID Type / Status
Subject Battle of Cuddalore (1783) E264551 entity
Predicate belligerent P375 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: [Battle of Cuddalore (1783), belligerent, Mysore]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mysore
Context triple: [Battle of Cuddalore (1783), belligerent, 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. 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.
  • 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_69d6aa9dafac8190bd90d2c74f661aa7 completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7e8a7f35481909f35feb94ef10e80 completed April 9, 2026, 5:58 p.m.
NED1 Entity disambiguation (via context triple) batch_69e509cd971c8190bdaa7b3c8a1f32f2 completed April 19, 2026, 4:58 p.m.
Created at: April 8, 2026, 9:29 p.m.