Triple

T22031883
Position Surface form Disambiguated ID Type / Status
Subject Munjong of Joseon E544105 entity
Predicate burialPlace P196 FINISHED
Object Hyeonreung 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: Hyeonreung | Statement: [Munjong of Joseon, burialPlace, Hyeonreung]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hyeonreung
Context triple: [Munjong of Joseon, burialPlace, Hyeonreung]
  • A. Hyeonreung chosen
    Hyeonreung is a royal tomb from Korea’s Joseon Dynasty, notable as one of the UNESCO-listed burial sites of its kings and queens.
  • B. Yi Hyang
    Yi Hyang, better known by his temple name Munjong of Joseon, was the fifth king of Korea’s Joseon dynasty, noted for his brief reign in the mid-15th century.
  • C. Junggyeong
    Junggyeong was one of the principal capital cities of the Balhae kingdom, serving as a key political and administrative center in Northeast Asia during the early medieval period.
  • D. Singyeong
    Singyeong was a monarch of the Later Baekje kingdom during Korea’s Later Three Kingdoms period.
  • E. Heon-teu
    Heon-teu is an alternative name for the term "Hunt," likely used as a transliteration or variant in another language or context.
  • 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_69e11e2f98c8819083e11eab90942a78 completed April 16, 2026, 5:36 p.m.
NER Named-entity recognition batch_69f127edd5b48190a9aeb2840105c181 completed April 28, 2026, 9:34 p.m.
Created at: April 16, 2026, 8:24 p.m.