Triple
T1576992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jung District |
E33675
|
entity |
| Predicate | hasRevisedRomanization |
P23170
|
FINISHED |
| Object |
Jung-gu
Jung-gu is a central urban district name used in several South Korean cities, typically encompassing key commercial, administrative, and cultural areas.
|
E170064
|
NE FINISHED |
How this triple was built (4 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: Jung-gu | Statement: [Jung District, hasRevisedRomanization, Jung-gu]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jung-gu Context triple: [Jung District, hasRevisedRomanization, Jung-gu]
-
A.
Jung-gu
Jung-gu is a central district of the metropolitan city of Daejeon in South Korea, known for its mix of commercial, residential, and administrative areas.
-
B.
Jung-gu
Jung-gu is a central administrative district of the metropolitan city of Ulsan in South Korea.
-
C.
Dong-gu
Dong-gu is a district-level administrative area within the metropolitan city of Daejeon in South Korea.
-
D.
Dong-gu
Dong-gu is an administrative district of the metropolitan city of Ulsan in South Korea, known for its coastal location and industrial facilities.
-
E.
Gangseo District
Gangseo District is a western coastal district of Busan, South Korea, known for its industrial complexes, logistics hubs, and proximity to Gimhae International Airport.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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: Jung-gu Triple: [Jung District, hasRevisedRomanization, Jung-gu]
Generated description
Jung-gu is a central urban district name used in several South Korean cities, typically encompassing key commercial, administrative, and cultural areas.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Jung-gu Target entity description: Jung-gu is a central urban district name used in several South Korean cities, typically encompassing key commercial, administrative, and cultural areas.
-
A.
Jung-gu
chosen
Jung-gu is a central district of the metropolitan city of Daejeon in South Korea, known for its mix of commercial, residential, and administrative areas.
-
B.
Jung-gu
Jung-gu is a central administrative district of the metropolitan city of Ulsan in South Korea.
-
C.
Dong-gu
Dong-gu is a district-level administrative area within the metropolitan city of Daejeon in South Korea.
-
D.
Dong-gu
Dong-gu is an administrative district of the metropolitan city of Ulsan in South Korea, known for its coastal location and industrial facilities.
-
E.
Gangseo District
Gangseo District is a western coastal district of Busan, South Korea, known for its industrial complexes, logistics hubs, and proximity to Gimhae International Airport.
- F. None of above.
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_69a885f27a4c8190a4622252cdf54c00 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a908d400c08190b0f5fc32ad500b80 |
completed | March 5, 2026, 4:38 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae5d78933c81908359b0010b9e6147 |
completed | March 9, 2026, 5:41 a.m. |
| NEDg | Description generation | batch_69ae5dd76d408190ab324280344c7b79 |
completed | March 9, 2026, 5:42 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69ae5e4bfda88190af66dcb564c1e731 |
completed | March 9, 2026, 5:44 a.m. |
Created at: March 4, 2026, 7:27 p.m.