Triple
T14089016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jung District, Seoul |
E339072
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Gwanghui-dong |
E1102478
|
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: Gwanghui-dong | Statement: [Jung District, Seoul, contains, Gwanghui-dong]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gwanghui-dong Context triple: [Jung District, Seoul, contains, Gwanghui-dong]
-
A.
Gwangbok-dong
Gwangbok-dong is a central commercial and cultural neighborhood in Busan, South Korea, known for its bustling shopping streets and proximity to major downtown attractions.
-
B.
Gwangan-dong
Gwangan-dong is a coastal neighborhood in Busan, South Korea, best known for Gwangalli Beach and its views of the illuminated Gwangan Bridge.
-
C.
Hwanghak-dong
chosen
Hwanghak-dong is a neighborhood in central Seoul, South Korea, known for its traditional flea markets and dense urban streetscape.
-
D.
Yongho-dong
Yongho-dong is a neighborhood in Busan, South Korea, known as a coastal residential area within the city's southern region.
-
E.
Hwagok-dong
Hwagok-dong is a neighborhood in western Seoul, South Korea, known as a residential and commercial area within Gangseo-gu.
- 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_69d81c687b0c819087fd9ed4198403f8 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de5ee1ce88819091c983286289337e |
completed | April 14, 2026, 3:36 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd7a2fdd7c8190b2ebf5a18c8039f2 |
completed | May 8, 2026, 5:52 a.m. |
Created at: April 9, 2026, 10:21 p.m.