Triple
T12000347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Busan Jung District |
E285640
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Donggwang-dong |
E690896
|
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: Donggwang-dong | Statement: [Busan Jung District, contains, Donggwang-dong]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Donggwang-dong Context triple: [Busan Jung District, contains, Donggwang-dong]
-
A.
Donggwang-dong
chosen
Donggwang-dong is a neighborhood (dong) located within Jung District in central Busan, South Korea, known for its urban setting and proximity to the city’s historic and commercial areas.
-
B.
Gwangan-dong
Gwangan-dong is a coastal neighborhood in Busan, South Korea, best known for Gwangalli Beach and its views of the illuminated Gwangan Bridge.
-
C.
Yeocheon-dong
Yeocheon-dong is a neighborhood in Ulsan, South Korea, known for encompassing the expansive Ulsan Grand Park.
-
D.
Jangjeon-dong
Jangjeon-dong is a neighborhood in Busan, South Korea, known as an administrative and residential center within Geumjeong District.
-
E.
Beomjeon-dong
Beomjeon-dong is a neighborhood (dong) located within Busanjin District in Busan, 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_69d6ab44a77c8190a652f4b27164e4ef |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903c26d7881909b67a31d04882eb5 |
completed | April 10, 2026, 2:05 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f67c5e9fbc819097cf9550378eabee |
completed | May 2, 2026, 10:36 p.m. |
Created at: April 8, 2026, 9:46 p.m.