Triple

T15876365
Position Surface form Disambiguated ID Type / Status
Subject Rakhine State E384961 entity
Predicate historicalName P65 FINISHED
Object Arakan E56814 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: Arakan | Statement: [Rakhine State, historicalName, Arakan]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Arakan
Context triple: [Rakhine State, historicalName, Arakan]
  • A. Arakan chosen
    Arakan is a historical coastal region in western Myanmar, now largely corresponding to Rakhine State and known for its distinct ethnic and cultural identity.
  • B. Arakan
    Arakan is a rural municipality in the province of Cotabato on the island of Mindanao in the Philippines, known for its agricultural economy and scenic highland landscapes.
  • C. Thayarwady
    Thayarwady is a town in central Myanmar known as an administrative and commercial center within the Bago Region.
  • D. Magway
    Magway is a city in central Myanmar situated on the Irrawaddy River, known as an administrative, commercial, and agricultural hub of the surrounding region.
  • E. Ta’ang
    Ta’ang is a Mon–Khmer language spoken primarily by the Ta’ang (Palaung) ethnic group in parts of Myanmar and neighboring regions.
  • 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_69d86da4e86481909f1325fdc971b5ec completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e155fdc1b881909d1c82c4c66a195a completed April 16, 2026, 9:34 p.m.
NED1 Entity disambiguation (via context triple) batch_69ffa950a890819092bc1e8895034593 completed May 9, 2026, 9:38 p.m.
Created at: April 10, 2026, 4:51 a.m.