Triple

T19595800
Position Surface form Disambiguated ID Type / Status
Subject Preah Ream E470344 entity
Predicate enemy P4567 FINISHED
Object Krung Reap NE NERFINISHED

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: Krung Reap | Statement: [Preah Ream, enemy, Krung Reap]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Krung Reap
Context triple: [Preah Ream, enemy, Krung Reap]
  • A. Krong Reap chosen
    Krong Reap is the primary demon antagonist in the Khmer epic Reamker, the Cambodian adaptation of the Ramayana.
  • B. Ang Thong city
    Ang Thong city is the capital and main urban center of Ang Thong Province in central Thailand, known for its traditional handicrafts and historic temples.
  • C. Wat Muang
    Wat Muang is a famous Buddhist temple in Thailand best known for housing one of the world’s largest seated Buddha statues.
  • D. Phra Nakhon
    Phra Nakhon is Bangkok’s historic central district, home to major cultural and political landmarks such as the Grand Palace and Wat Pho.
  • E. Bueng Kan
    Bueng Kan is a northeastern Thai city known as the capital of Bueng Kan Province, situated along the Mekong River near the border with Laos.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8e510024481908415c0d616fa6186 completed April 10, 2026, 11:54 a.m.
NER Named-entity recognition batch_69e6407a09608190aa1df92f8c21f9e7 completed April 20, 2026, 3:04 p.m.
Created at: April 10, 2026, 1:43 p.m.