Triple
T9812595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suyŏng-gu |
E238309
|
entity |
| Predicate | romanization |
P2508
|
FINISHED |
| Object | Suyŏng-gu |
E238309
|
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: Suyŏng-gu | Statement: [Suyŏng-gu, romanization, Suyŏng-gu]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Suyŏng-gu Context triple: [Suyŏng-gu, romanization, Suyŏng-gu]
-
A.
Suyŏng-gu
chosen
Suyŏng-gu is an urban district of Busan, South Korea, known for its coastal location and role as a residential and commercial hub within the city.
-
B.
Sŏch'o-gu
Sŏch'o-gu is the McCune–Reischauer romanization of Seocho District, a major administrative and residential area in southern Seoul, South Korea.
-
C.
Yŏngdŭngp'o-gu
Yŏngdŭngp'o-gu is a major district in southwestern Seoul, South Korea, known for its commercial centers, dense urban development, and transportation hubs.
-
D.
Kŭmchŏng-gu
Kŭmchŏng-gu is the McCune–Reischauer romanization of Geumjeong District, an administrative district in Busan, South Korea.
-
E.
Geumjeong-gu
Geumjeong-gu is a district in Busan, South Korea, known for its residential areas, transportation hubs, and proximity to Geumjeongsan Mountain.
- 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_69ca84defac48190abc1148804f184c1 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb222ba788190a9085272a3de7852 |
completed | April 2, 2026, 12:02 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d7fb12ac9c819087a182c12653792c |
completed | April 9, 2026, 7:16 p.m. |
Created at: March 30, 2026, 8:30 p.m.