Triple

T7467789
Position Surface form Disambiguated ID Type / Status
Subject Rigu E176418 entity
Predicate associatedWithRegion P285 FINISHED
Object Assam, India E4843 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: Assam, India | Statement: [Rigu, associatedWithRegion, Assam, India]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Assam, India
Context triple: [Rigu, associatedWithRegion, Assam, India]
  • A. Assam chosen
    Assam is a northeastern region of the Indian subcontinent known for its tea plantations, rich biodiversity, and distinct cultural heritage.
  • B. Tripura
    Tripura is a small, hilly state in northeastern India known for its diverse tribal cultures, historical palaces, and dense forests.
  • C. Arunachal Pradesh
    Arunachal Pradesh is a northeastern Indian state known for its mountainous terrain, diverse indigenous cultures, and strategic location along the borders with China, Bhutan, and Myanmar.
  • D. Manipur
    Manipur is a northeastern Indian state known for its scenic hills and valleys, rich indigenous cultures, and capital city Imphal.
  • E. Goalpara, Assam, India
    Goalpara is a town and district headquarters in western Assam, India, known for its cultural diversity and scenic location along the Brahmaputra River.
  • 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_69c69f223fd88190b4c69b95d7cbeeda completed March 27, 2026, 3:15 p.m.
NER Named-entity recognition batch_69c6f3f589cc81909f25268838c7c964 completed March 27, 2026, 9:17 p.m.
NED1 Entity disambiguation (via context triple) batch_69c89a712fdc8190998d9a05dc73f40c completed March 29, 2026, 3:20 a.m.
Created at: March 27, 2026, 3:40 p.m.