Triple
T34726868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Geumgwan Gaya |
E1001094
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Korean city-state |
C61965
|
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 city-state Context triple: [Geumgwan Gaya, instanceOf, ancient Korean city-state]
-
A.
Balhae capital
The Balhae capital is the primary political, administrative, and cultural center of the Balhae kingdom, serving as the seat of its monarch and central institutions.
-
B.
one of the Three Kingdoms of Korea
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.
ancient Japanese city
An ancient Japanese city is a historical urban center in Japan characterized by traditional wooden architecture, temples and shrines, and a layout reflecting the political, cultural, and religious life of its era.
-
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.
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.
- F. None of above. chosen
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_69f76daeb6e48190a4c9a6b0edc80f72 |
completed | May 3, 2026, 3:45 p.m. |
Created at: May 3, 2026, 3:59 p.m.