Triple

T16928395
Position Surface form Disambiguated ID Type / Status
Subject Yongin E410636 entity
Predicate hasRomanizedName P2508 FINISHED
Object Yongin-si E410636 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: Yongin-si | Statement: [Yongin, hasRomanizedName, Yongin-si]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Yongin-si
Context triple: [Yongin, hasRomanizedName, Yongin-si]
  • A. Yongin chosen
    Yongin is a rapidly growing city in the Seoul Capital Area of South Korea, known for attractions like Everland Resort and the Korean Folk Village.
  • B. Dongducheon
    Dongducheon is a city in northern South Korea known for its proximity to the Demilitarized Zone and the presence of U.S. military bases.
  • C. Uijeongbu
    Uijeongbu is a city in South Korea known as a suburban hub north of Seoul, featuring residential districts, commercial centers, and a history of hosting U.S. military bases.
  • D. Anseong
    Anseong is a city in Gyeonggi Province, South Korea, known for its traditional culture, agricultural heritage, and annual Baudeogi Festival.
  • E. Gwacheon
    Gwacheon is a small city in South Korea known for hosting major government offices, cultural institutions, and the Seoul Grand Park complex.
  • 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_69d886c7b1e481908c3766dfa8c13458 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3cdf3fc3c8190a884f7ecd5c47adb completed April 18, 2026, 6:31 p.m.
NED1 Entity disambiguation (via context triple) batch_6a011b3bb69081908805c30d50242eb6 completed May 10, 2026, 11:56 p.m.
Created at: April 10, 2026, 5:30 a.m.