Triple
T7840338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jung-gu, Ulsan |
E181788
|
entity |
| Predicate | borderedBy |
P224
|
FINISHED |
| Object | Dong-gu, Ulsan |
E182488
|
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: Dong-gu, Ulsan | Statement: [Jung-gu, Ulsan, borderedBy, Dong-gu, Ulsan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Dong-gu, Ulsan Context triple: [Jung-gu, Ulsan, borderedBy, Dong-gu, Ulsan]
-
A.
Jung-gu, Ulsan
Jung-gu, Ulsan is a central district of the metropolitan city of Ulsan in South Korea, known for its administrative, commercial, and residential functions.
-
B.
Dong-gu, Busan
Dong-gu, Busan is a central district of Busan, South Korea, known for its major transportation hubs, dense urban neighborhoods, and coastal views.
-
C.
Buk-gu, Ulsan
Buk-gu, Ulsan is a northern district of the metropolitan city of Ulsan in South Korea, known for its mix of residential areas, industrial facilities, and coastal landscapes.
-
D.
Dong-gu
Dong-gu is a district-level administrative area within the metropolitan city of Daejeon in South Korea.
-
E.
Dong-gu
chosen
Dong-gu is an administrative district of the metropolitan city of Ulsan in South Korea, known for its coastal location and industrial facilities.
- 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_69cc639b68a4819080acfca35e498cfa |
completed | April 1, 2026, 12:15 a.m. |
Created at: March 30, 2026, 4:47 p.m.