Triple
T12420213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kŭmchŏng-gu |
E296748
|
entity |
| Predicate | romanizes |
P2508
|
FINISHED |
| Object | Geumjeong-gu |
E774985
|
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: Geumjeong-gu | Statement: [Kŭmchŏng-gu, romanizes, Geumjeong-gu]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Geumjeong-gu Context triple: [Kŭmchŏng-gu, romanizes, Geumjeong-gu]
-
A.
Geumjeong-gu
chosen
Geumjeong-gu is a district in Busan, South Korea, known for its residential areas, transportation hubs, and proximity to Geumjeongsan Mountain.
-
B.
Suyeong-gu
Suyeong-gu is a coastal district in the city of Busan, South Korea, known for its urban neighborhoods and proximity to popular beaches.
-
C.
Yeonsu-gu
Yeonsu-gu is an administrative district of Incheon, South Korea, known for its coastal location, modern residential areas, and proximity to the Songdo International Business District.
-
D.
Kangseo-gu
Kangseo-gu is the romanized name of Gangseo District, an administrative district of Seoul, South Korea.
-
E.
Jinhae-gu
Jinhae-gu is a coastal district in Changwon, South Korea, best known for its large naval base and famous annual cherry blossom festival.
- 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_69d6ada0640c81908c061d7fb3d47786 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94d6efd748190a5d9396a343e41e1 |
completed | April 10, 2026, 7:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f739668f3481909cc7564c3ede2896 |
completed | May 3, 2026, 12:02 p.m. |
Created at: April 8, 2026, 9:55 p.m.