Triple

T8850638
Position Surface form Disambiguated ID Type / Status
Subject Balhae E210628 entity
Predicate instanceOf P0 FINISHED
Object successor state of Goguryeo C14309 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: successor state of Goguryeo
Context triple: [Balhae, instanceOf, successor state of Goguryeo]
  • A. 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.
  • B. Jurchen-led state chosen
    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.
  • C. Mongol successor state
    A Mongol successor state is a political entity that emerged from the fragmentation of the Mongol Empire, inheriting its territories, institutions, and ruling elites while developing distinct regional identities and governance structures.
  • D. Bugis principality
    A Bugis principality is a traditional political entity or small sovereign state historically governed by Bugis rulers in South Sulawesi, Indonesia, characterized by its own leadership, territory, and customary laws.
  • 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.

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_69ca838a424c8190b1ecac115c2927e7 completed March 30, 2026, 2:07 p.m.
Created at: March 30, 2026, 6:49 p.m.