Triple

T9502967
Position Surface form Disambiguated ID Type / Status
Subject Tripuri people E229188 entity
Predicate ethnicity P194 FINISHED
Object Tripuri E688203 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: Tripuri | Statement: [Tripuri people, ethnicity, Tripuri]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tripuri
Context triple: [Tripuri people, ethnicity, Tripuri]
  • A. Tripuri chosen
    The Tripuri are an indigenous ethnic group of the Indian subcontinent, primarily associated with the state of Tripura and surrounding regions of northeast India and eastern Bangladesh, known for their distinct Tibeto-Burman language, culture, and traditions.
  • B. Vikrampura
    Vikrampura was an important historical city that served as a principal royal center of the medieval Indian Pala dynasty in eastern India.
  • C. Brahmapuri
    Brahmapuri is a town in Maharashtra, India, known as one of the important urban centers within Chandrapur district.
  • D. Karanpur
    Karanpur is a town located in the Ganganagar district of the northern Indian state of Rajasthan.
  • E. Tathra
    Tathra is a coastal town on the Sapphire Coast of New South Wales, Australia, known for its historic wharf, scenic beaches, and fishing.
  • 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_69ca847611c48190a28c028644198c75 completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cd983ea6048190a2d7924c8e6d1fbc completed April 1, 2026, 10:12 p.m.
NED1 Entity disambiguation (via context triple) batch_69d13a10f7b08190b8e4d4bc3b9815c6 completed April 4, 2026, 4:19 p.m.
Created at: March 30, 2026, 7:57 p.m.