Triple

T1486572
Position Surface form Disambiguated ID Type / Status
Subject Karnataka E29477 entity
Predicate hasCity P316 FINISHED
Object Mangaluru E156874 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: Mangaluru | Statement: [Karnataka, hasCity, Mangaluru]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mangaluru
Context triple: [Karnataka, hasCity, Mangaluru]
  • A. Mangalore chosen
    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.
  • B. Mysuru
    Mysuru is a historic city in the southern Indian state of Karnataka, renowned for its royal heritage, palaces, and cultural festivals such as Dasara.
  • C. Bengaluru
    Bengaluru is a major Indian metropolis known as the country’s leading technology and innovation hub, often called the “Silicon Valley of India.”
  • D. Thiruvananthapuram
    Thiruvananthapuram is the capital city of the Indian state of Kerala, known for its political importance, educational institutions, and rich cultural heritage.
  • E. Kannur
    Kannur is a historic coastal city in the Indian state of Kerala, known for its role in maritime trade, colonial-era forts, and rich Theyyam ritual art traditions.
  • 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_69a498da82e08190ba833330d05f380f completed March 1, 2026, 7:51 p.m.
NER Named-entity recognition batch_69a4c6a3325881909bbc55efc04ad60f completed March 1, 2026, 11:07 p.m.
NED1 Entity disambiguation (via context triple) batch_69ad1ca4c4e481909ea0ca76841454b1 completed March 8, 2026, 6:52 a.m.
Created at: March 1, 2026, 8:12 p.m.