Triple
T7131356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jung District, Busan |
E166194
|
entity |
| Predicate | romanization |
P2508
|
FINISHED |
| Object | Busan Jung-gu |
E285640
|
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: Busan Jung-gu | Statement: [Jung District, Busan, romanization, Busan Jung-gu]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Busan Jung-gu Context triple: [Jung District, Busan, romanization, Busan Jung-gu]
-
A.
Busan Jung District
chosen
Busan Jung District is a central urban district of Busan, South Korea, known for its historic downtown area, bustling commercial streets, and major shopping and cultural attractions.
-
B.
Busanjin District
Busanjin District is a central urban district of Busan, South Korea, known as a major commercial and transportation hub of the city.
-
C.
Pusanjin-gu
Pusanjin-gu is a central urban district of Busan, South Korea, known for its major commercial areas, transportation hubs, and dense residential neighborhoods.
-
D.
Dong-gu
Dong-gu is a district-level administrative area within the metropolitan city of Daejeon in South Korea.
-
E.
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.
- 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_69c68884a9388190af42f90d1c1a7151 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e66f15b88190bc1fb0f0a8af16a6 |
completed | March 27, 2026, 8:19 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c968c9a1a48190b6ea5bb08ff745af |
completed | March 29, 2026, 6 p.m. |
Created at: March 27, 2026, 2:44 p.m.