Triple
T19529230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jin (Korean state) |
E488615
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Korean state |
C16919
|
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: ancient Korean state Context triple: [Jin (Korean state), instanceOf, ancient Korean state]
-
A.
ancient Chinese state
An ancient Chinese state is a historically documented political entity that existed within the territory of what is now China, characterized by its own ruling house, administrative system, culture, and military, and interacting with neighboring states through warfare, diplomacy, and trade.
-
B.
one of the Three Kingdoms of Korea
chosen
One of the Three Kingdoms of Korea is a major ancient Korean state—Goguryeo, Baekje, or Silla—that existed between the 1st century BCE and 7th century CE and played a central role in shaping early Korean history, culture, and territorial formation.
-
C.
Jurchen-led state
A Jurchen-led state is a political entity in which the Jurchen people hold primary ruling authority, shaping its governance, military organization, and cultural policies.
-
D.
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.
-
E.
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.
- 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_69d8e8da8bec819081f400199491ccc3 |
completed | April 10, 2026, 12:11 p.m. |
Created at: April 10, 2026, 1:41 p.m.