Triple
T6774636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ulsan-gwangyeoksi |
E155125
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | City in South Korea |
C21194
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: City in South Korea Context triple: [Ulsan-gwangyeoksi, instanceOf, City in South Korea]
-
A.
city in South Korea
chosen
A city in South Korea is an urban administrative division governed by local authorities, characterized by concentrated population, infrastructure, and economic, cultural, and social activities within the Republic of Korea.
-
B.
special city in South Korea
A special city in South Korea is a top-level administrative division that functions as a city with the same status as a province, directly governed by the central government and typically encompassing a large urban area.
-
C.
Autonomous district of South Korea
An autonomous district of South Korea is a self-governing municipal subdivision within a metropolitan city or special city that has its own local government and administrative authority over local affairs.
-
D.
province of South Korea
A province of South Korea is a primary administrative division of the country, governed by a provincial government that oversees regional affairs, services, and development across multiple cities and counties.
-
E.
South Korean company
A South Korean company is a business entity legally registered and operating in South Korea, typically structured under its corporate laws and engaged in commercial, industrial, or service activities within domestic and global markets.
- F. None of above.
Provenance (1 batch)
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_69c68812ef7c819099369f51febb725c |
completed | March 27, 2026, 1:37 p.m. |
Created at: March 27, 2026, 2:13 p.m.