Triple

T2136376
Position Surface form Disambiguated ID Type / Status
Subject Barak Valley E46662 entity
Predicate administrativeDivisionOf P747 FINISHED
Object Assam 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 | Statement: [Barak Valley, administrativeDivisionOf, Assam]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Assam
Context triple: [Barak Valley, administrativeDivisionOf, Assam]
  • 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. West Bengal
    West Bengal is an eastern Indian state known for its cultural heritage, literature, and the metropolis of Kolkata (formerly Calcutta).
  • E. Meghalaya
    Meghalaya is a hilly state in northeastern India known for its heavy rainfall, lush forests, and diverse indigenous cultures.
  • 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_69a88a174ab48190a5db20c132e5dccf completed March 4, 2026, 7:37 p.m.
NER Named-entity recognition batch_69abbdc4ce8c81908d143d5451681e6a completed March 7, 2026, 5:55 a.m.
NED1 Entity disambiguation (via context triple) batch_69b24a7f3c5c8190b742a45a50c74ca8 completed March 12, 2026, 5:09 a.m.
Created at: March 4, 2026, 7:44 p.m.