Triple
T7313281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buk-gu, Ulsan |
E168146
|
entity |
| Predicate | subdivisionName |
P747
|
FINISHED |
| Object | Buk-gu |
E168146
|
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: Buk-gu | Statement: [Buk-gu, Ulsan, subdivisionName, Buk-gu]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Buk-gu Context triple: [Buk-gu, Ulsan, subdivisionName, Buk-gu]
-
A.
Buk-gu
Buk-gu is a northern administrative district of Daegu, South Korea, known for its residential neighborhoods, educational institutions, and commercial areas.
-
B.
Buk-gu
chosen
Buk-gu is a northern administrative district of the metropolitan city of Ulsan in South Korea.
-
C.
Donggureung
Donggureung is a large royal burial complex in Guri, South Korea, containing multiple tombs of Joseon Dynasty kings and queens and recognized as part of a UNESCO World Heritage site.
-
D.
Taebong
Taebong was a short-lived Korean kingdom of the early 10th century that emerged during the Later Three Kingdoms period before being absorbed by Goryeo.
-
E.
Gwangalli
Gwangalli is a coastal neighborhood in Busan, South Korea, best known for its sandy beach, vibrant nightlife, and scenic views of the nearby Gwangan Bridge.
- 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_69c6888d8e3c81909db79714903baf31 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6ec02319c819096d25e3683943886 |
completed | March 27, 2026, 8:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7eeeedea88190a17cf6b83abc10d8 |
completed | March 28, 2026, 3:08 p.m. |
Created at: March 27, 2026, 3:02 p.m.