Triple

T6774642
Position Surface form Disambiguated ID Type / Status
Subject Ulsan-gwangyeoksi E155125 entity
Predicate borders P224 FINISHED
Object Gyeongju E241549 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: Gyeongju | Statement: [Ulsan-gwangyeoksi, borders, Gyeongju]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gyeongju
Context triple: [Ulsan-gwangyeoksi, borders, 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. 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.
  • D. 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.
  • E. Cheongju
    Cheongju is a major city in central South Korea that serves as the capital of North Chungcheong Province and an important regional administrative, educational, and transportation hub.
  • 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_69c68812ef7c819099369f51febb725c completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6d24ddaf08190baffbff991eeb458 completed March 27, 2026, 6:54 p.m.
NED1 Entity disambiguation (via context triple) batch_69cb59a7732c819095aa0903d419b740 completed March 31, 2026, 5:20 a.m.
Created at: March 27, 2026, 2:13 p.m.