Triple

T5068324
Position Surface form Disambiguated ID Type / Status
Subject Goguryeo E114197 entity
Predicate predecessor P97 FINISHED
Object Buyeo E488614 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: Buyeo | Statement: [Goguryeo, predecessor, Buyeo]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Buyeo
Context triple: [Goguryeo, predecessor, Buyeo]
  • A. Buyeo chosen
    Buyeo was an ancient Korean kingdom that emerged in northern Manchuria and northern Korea, playing a key role in the early formation of Korean states and culture.
  • B. Meiktila
    Meiktila is a city in central Myanmar that served as a key strategic location during World War II, particularly in the Burma Campaign.
  • C. Seogwipo
    Seogwipo is a coastal city on South Korea’s Jeju Island known for its waterfalls, volcanic landscapes, and popular tourist attractions.
  • D. Gyeongju
    Gyeongju is a historic city in South Korea famed for its rich cultural heritage and numerous archaeological sites from the ancient Silla Kingdom.
  • E. Gimhae
    Gimhae is a city in South Gyeongsang Province, South Korea, known for its historical significance as the birthplace of the ancient Gaya confederacy and its proximity to the metropolitan city of Busan.
  • 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_69bd443cf28c8190ad371d603563dbdd completed March 20, 2026, 12:57 p.m.
NER Named-entity recognition batch_69bd749dd1a08190858fa739df024eb4 completed March 20, 2026, 4:23 p.m.
NED1 Entity disambiguation (via context triple) batch_69bea4a027a88190a515a374e5405d8a completed March 21, 2026, 2:01 p.m.
Created at: March 20, 2026, 1:39 p.m.