Triple

T9960597
Position Surface form Disambiguated ID Type / Status
Subject Gwangmu Reform E195556 entity
Predicate inception P61 FINISHED
Object Gwangmu era E754191 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: Gwangmu era | Statement: [Gwangmu Reform, inception, Gwangmu era]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gwangmu era
Context triple: [Gwangmu Reform, inception, Gwangmu era]
  • A. Gwangmu chosen
    Gwangmu was the era name associated with Emperor Gojong’s reign during Korea’s transition from the Joseon dynasty to the Korean Empire in the late 19th and early 20th centuries.
  • B. Kaiyuan era
    The Kaiyuan era was a prosperous and culturally flourishing period during the reign of Emperor Xuanzong in the High Tang dynasty of China.
  • C. Gaegyeong
    Gaegyeong was the principal royal and administrative capital of the Korean kingdom of Goryeo, located in what is now Kaesong, North Korea.
  • D. Goryeo
    Goryeo was a medieval Korean dynasty (918–1392) that unified much of the Korean Peninsula and gave Korea its modern name.
  • E. Yuanhe era
    The Yuanhe era was a regnal period in the early 9th century during the Tang dynasty, marked by Emperor Xianzong’s efforts to reassert central imperial authority over powerful regional warlords.
  • 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_69ca82eaaa008190a54fa1a9f954b9ad completed March 30, 2026, 2:04 p.m.
NER Named-entity recognition batch_69cdb6d219c48190b2084b0eb07ae125 completed April 2, 2026, 12:22 a.m.
NED1 Entity disambiguation (via context triple) batch_69d257aa73d4819081f77f8386449905 completed April 5, 2026, 12:38 p.m.
Created at: March 30, 2026, 8:47 p.m.