Triple
T10834857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bujeon-dong |
E255726
|
entity |
| Predicate | hasRomanizedName |
P2508
|
FINISHED |
| Object | Bujeon-dong |
E255726
|
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: Bujeon-dong | Statement: [Bujeon-dong, hasRomanizedName, Bujeon-dong]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bujeon-dong Context triple: [Bujeon-dong, hasRomanizedName, Bujeon-dong]
-
A.
Bujeon-dong
chosen
Bujeon-dong is a neighborhood in Busan, South Korea, known as a busy commercial and transportation hub with markets, shops, and access to major train and subway lines.
-
B.
Beomjeon-dong
Beomjeon-dong is a neighborhood (dong) located within Busanjin District in Busan, South Korea.
-
C.
Bupyeong-dong
Bupyeong-dong is a central neighborhood and administrative hub within Bupyeong District in Incheon, South Korea.
-
D.
Beomcheon-dong
Beomcheon-dong is a neighborhood in Busan, South Korea, known as a residential and commercial area within the central Busanjin District.
-
E.
Bumjin-dong
Bumjin-dong is a neighborhood (dong) located within Pusanjin 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_69d6aa81a5d08190aa86689061d1ddd2 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d74425447081908fb51c7edf54af67 |
completed | April 9, 2026, 6:16 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ef1243b14081909d07ab0ebb32cc68 |
completed | April 27, 2026, 7:37 a.m. |
Created at: April 8, 2026, 9:19 p.m.