Triple

T10730344
Position Surface form Disambiguated ID Type / Status
Subject Eumseong-eup E253053 entity
Predicate romanization P2508 FINISHED
Object Eumseong-up E253053 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: Eumseong-up | Statement: [Eumseong-eup, romanization, Eumseong-up]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Eumseong-up
Context triple: [Eumseong-eup, romanization, Eumseong-up]
  • A. Eumseong-eup chosen
    Eumseong-eup is the main urban township and administrative center of Eumseong County in North Chungcheong Province, South Korea.
  • B. Eumseong-gun
    Eumseong-gun is a rural county in central South Korea known for its agricultural production and location within North Chungcheong Province.
  • C. Geumwang-eup
    Geumwang-eup is a town-level administrative division in Eumseong County, located in North Chungcheong Province, South Korea.
  • D. Mokneung
    Mokneung is one of the royal burial sites from Korea’s Joseon Dynasty, forming part of the UNESCO-listed Royal Tombs complex.
  • E. Mungyeong
    Mungyeong is a city in South Korea known for its historic mountain passes, scenic hiking trails, and traditional cultural heritage.
  • 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_69d6aa5d8be481909a43218b2bfdbe95 completed April 8, 2026, 7:19 p.m.
NER Named-entity recognition batch_69d70fcb1cd881909635def59ad5d19c completed April 9, 2026, 2:32 a.m.
NED1 Entity disambiguation (via context triple) batch_69e55621a88c8190b9611bf9e3b307de completed April 19, 2026, 10:24 p.m.
Created at: April 8, 2026, 9:14 p.m.