Triple
T14762576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seodaemun-gu |
E346906
|
entity |
| Predicate | locatedInRegion |
P40
|
FINISHED |
| Object | Sudogwon |
E227776
|
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: Sudogwon | Statement: [Seodaemun-gu, locatedInRegion, Sudogwon]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sudogwon Context triple: [Seodaemun-gu, locatedInRegion, Sudogwon]
-
A.
Sudogwon
chosen
Sudogwon is the Seoul Capital Area of South Korea, encompassing Seoul, Incheon, and surrounding Gyeonggi Province as the country’s largest and most populous metropolitan region.
-
B.
Gwangalli
Gwangalli is a coastal neighborhood in Busan, South Korea, best known for its sandy beach, vibrant nightlife, and scenic views of the nearby Gwangan Bridge.
-
C.
Seochon
Seochon is a historic neighborhood in central Seoul known for its traditional hanok houses, narrow alleyways, and vibrant mix of old Korean culture and modern cafes and galleries.
-
D.
Wiryeseong
Wiryeseong was the first capital city of the ancient Korean kingdom of Baekje, located in the Han River basin near present-day Seoul.
-
E.
Won-dong
Won-dong is a neighborhood (dong) within the city of Osan in Gyeonggi Province, South Korea.
- 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_69d822e8896c819091169882f9b20486 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec7f3a1608190b1b17624003a0c7f |
completed | April 14, 2026, 11:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe0cf24c0081909221cb7d761e882f |
completed | May 8, 2026, 4:18 p.m. |
Created at: April 10, 2026, 1:30 a.m.