Triple
T7840330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jung-gu, Ulsan |
E181788
|
entity |
| Predicate | romanization |
P2508
|
FINISHED |
| Object | Jung-gu |
E181788
|
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: Jung-gu | Statement: [Jung-gu, Ulsan, romanization, Jung-gu]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jung-gu Context triple: [Jung-gu, Ulsan, romanization, Jung-gu]
-
A.
Jung-gu
Jung-gu is a central district of the metropolitan city of Daejeon in South Korea, known for its mix of commercial, residential, and administrative areas.
-
B.
Jung-gu
chosen
Jung-gu is a central administrative district of the metropolitan city of Ulsan in South Korea.
-
C.
Jung-gu
Jung-gu is a central urban district of Daegu, South Korea, known for its dense commercial areas, historic sites, and administrative importance.
-
D.
Jung-gu
Jung-gu is a central urban district name used in several major South Korean cities, typically encompassing key commercial, administrative, and cultural areas.
-
E.
Jung-gu
Jung-gu is a central district of Busan, South Korea, known for its historic markets, port-side location, and dense urban commercial areas.
- 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_69ca8285d6488190a95d4c02d7354b53 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb14c589748190b34d0911d373e194 |
completed | March 31, 2026, 12:26 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cd66ecea6c819097a74513c5d84193 |
completed | April 1, 2026, 6:41 p.m. |
Created at: March 30, 2026, 4:47 p.m.