Triple

T2873288
Position Surface form Disambiguated ID Type / Status
Subject Shan E56815 entity
Predicate historicalRegion P915 FINISHED
Object Shan States E75189 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: Shan States | Statement: [Shan, historicalRegion, Shan States]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Shan States
Context triple: [Shan, historicalRegion, Shan States]
  • A. Shan States chosen
    The Shan States were a collection of semi-autonomous, traditionally ruled principalities in what is now eastern Myanmar, historically inhabited by the Shan people and later organized as a distinct administrative region under British colonial rule.
  • B. Rajpipla State
    Rajpipla State was a former princely state in British India, located in present-day Gujarat.
  • C. Virpur State
    Virpur State was a former princely state in western India historically governed by the Jadeja Rajput dynasty.
  • D. Shekhawati
    Shekhawati is a dialect of the Rajasthani language spoken primarily in the Shekhawati region of northern Rajasthan, India.
  • E. Nawanagar State
    Nawanagar State was a former princely state in western India, ruled by the Jadeja Rajput dynasty with its capital at Jamnagar, and later integrated into the modern state of Gujarat.
  • 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_69ab4a4ced288190ab6d3e062d10f7f6 completed March 6, 2026, 9:42 p.m.
NER Named-entity recognition batch_69abdfe59ef88190b8bdfdd03e8965f3 completed March 7, 2026, 8:20 a.m.
NED1 Entity disambiguation (via context triple) batch_69b03153b5048190925bfacc07f2db66 completed March 10, 2026, 2:57 p.m.
Created at: March 6, 2026, 10:03 p.m.