Triple
T1586634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Busanjin District |
E34080
|
entity |
| Predicate | romanization |
P2508
|
FINISHED |
| Object | Busanjin-gu |
E34080
|
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: Busanjin-gu | Statement: [Busanjin District, romanization, Busanjin-gu]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Busanjin-gu Context triple: [Busanjin District, romanization, Busanjin-gu]
-
A.
Busanjin District
chosen
Busanjin District is a central urban district of Busan, South Korea, known as a major commercial and transportation hub of the city.
-
B.
Dongnae District
Dongnae District is a historic and central administrative district of Busan, South Korea, known for its hot springs and cultural heritage sites.
-
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.
Jung-gu
Jung-gu is a central administrative district of the metropolitan city of Ulsan in 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_69a885fceb2c8190b47e0f7c0aefbff0 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a908f3b5f48190bd5eff3ce81c5ffb |
completed | March 5, 2026, 4:39 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae6adcef5881908cefd7d575b85323 |
completed | March 9, 2026, 6:38 a.m. |
Created at: March 4, 2026, 7:27 p.m.