Triple

T33377234
Position Surface form Disambiguated ID Type / Status
Subject Ilsanseo-gu E854667 entity
Predicate hasMcCuneReischauerRomanization P23170 FINISHED
Object Ilsansŏ-gu
Ilsansŏ-gu is a district of Goyang in Gyeonggi Province, South Korea, known as a planned residential and commercial area within the Seoul Capital Area.
E2291682 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: Ilsansŏ-gu | Statement: [Ilsanseo-gu, hasMcCuneReischauerRomanization, Ilsansŏ-gu]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Ilsansŏ-gu
Triple: [Ilsanseo-gu, hasMcCuneReischauerRomanization, Ilsansŏ-gu]
Generated description
Ilsansŏ-gu is a district of Goyang in Gyeonggi Province, South Korea, known as a planned residential and commercial area within the Seoul Capital Area.

Provenance (5 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_69f3496ca10c8190908640d18fa00832 completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f6dfff88848190833cb929eab3c818 completed May 3, 2026, 5:41 a.m.
NED1 Entity disambiguation (via context triple) batch_6a5c7c61be1c8190a5a3dbfef97888e3 completed July 19, 2026, 7:27 a.m.
NEDg Description generation batch_6a5c7df92a008190bd056e385ea60417 completed July 19, 2026, 7:34 a.m.
NED2 Entity disambiguation (via description) batch_6a5c7e491c288190a5912fcc8cd2ab56 completed July 19, 2026, 7:35 a.m.
Created at: May 1, 2026, 1:35 a.m.