Triple

T3104293
Position Surface form Disambiguated ID Type / Status
Subject Korat, Thailand E64793 entity
Predicate locatedOn P40 FINISHED
Object Khorat Plateau E327357 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: Khorat Plateau | Statement: [Korat, Thailand, locatedOn, Khorat Plateau]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Khorat Plateau
Context triple: [Korat, Thailand, locatedOn, Khorat Plateau]
  • A. Khorat Plateau chosen
    The Khorat Plateau is a large, elevated region in northeastern Thailand known for its agricultural landscapes and distinct geology.
  • B. Tenasserim
    Tenasserim is a long, narrow coastal region in southern Myanmar along the Andaman Sea, historically significant as a frontier area between Burmese and Thai kingdoms.
  • C. Chiengmai
    Chiengmai is an alternative spelling of Chiang Mai, a major cultural and historical city in northern Thailand known for its temples and mountainous surroundings.
  • D. Tenasserim Hills
    Tenasserim Hills is a long mountain range forming a natural border between Myanmar and Thailand on the Indochinese Peninsula.
  • E. Somkheti Range
    Somkheti Range is a mountain range forming part of the Lesser Caucasus system in the South Caucasus region.
  • 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_69ad857eeaf48190b34ebfdaa7a264cf completed March 8, 2026, 2:19 p.m.
NER Named-entity recognition batch_69ada26f376c8190a049399e33314d52 completed March 8, 2026, 4:23 p.m.
NED1 Entity disambiguation (via context triple) batch_69b20f5994088190abc4b56040922c16 completed March 12, 2026, 12:56 a.m.
Created at: March 8, 2026, 3:03 p.m.