Triple

T20099518
Position Surface form Disambiguated ID Type / Status
Subject King Munmu E496495 entity
Predicate capital P234 FINISHED
Object Gyeongju NE NERFINISHED

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: Gyeongju | Statement: [King Munmu, capital, Gyeongju]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gyeongju
Context triple: [King Munmu, capital, Gyeongju]
  • A. Gyeongju chosen
    Gyeongju is a historic city in South Korea famed for its rich cultural heritage and numerous archaeological sites from the ancient Silla Kingdom.
  • B. Yeongju
    Yeongju is a city in eastern South Korea known for its historic temples, Confucian academies, and scenic mountainous landscapes.
  • C. Kyŏngju-si
    Kyŏngju-si is a historic coastal city in southeastern South Korea renowned for its rich Silla Dynasty heritage, ancient temples, and numerous UNESCO World Heritage sites.
  • D. Jinju-si
    Jinju-si is a city in South Gyeongsang Province, South Korea, known for its historic Jinju Fortress and the annual Namgang Yudeung (Lantern) Festival.
  • 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 (2 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_69da626eee3881909f3454986d4a6511 completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e6666f2298819089659f13556ca305 completed April 20, 2026, 5:46 p.m.
Created at: April 11, 2026, 11:26 p.m.