Triple

T24123596
Position Surface form Disambiguated ID Type / Status
Subject Gyeongju Kim clan E597729 entity
Predicate hasBonGwanInHanja P27905 FINISHED
Object 慶州
慶州（慶州／경주）は、韓国南東部の慶尚北道に位置し、新羅王朝の古都として多くの歴史遺跡と文化財を有する都市である。
 E1615400 NE FINISHED

How this triple was built (3 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: 慶州 | Statement: [Gyeongju Kim clan, hasBonGwanInHanja, 慶州]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: 慶州
Triple: [Gyeongju Kim clan, hasBonGwanInHanja, 慶州]
Generated description
慶州（慶州／경주）は、韓国南東部の慶尚北道に位置し、新羅王朝の古都として多くの歴史遺跡と文化財を有する都市である。
PD Predicate disambiguation gpt-5-mini-2025-08-07 
Target predicate: hasBonGwanInHanja
Context triple: [Gyeongju Kim clan, hasBonGwanInHanja, 慶州]
  • A. hanjaName chosen
    Indicates that one entity is the Sino-Korean (hanja) written form corresponding to the name of another entity.
  • B. hasHangulName
    Indicates that an entity is associated with a name written in the Korean Hangul script.
  • C. usesHanjaVariants
    Indicates that one entity employs or incorporates alternative Hanja (Chinese character) forms corresponding to another entity.
  • D. hasTraditionalCharacter
    Indicates that an entity is associated with or represented by a traditional (non-simplified or historically established) written character form.
  • E. hasNameInKanji
    Indicates that an entity is associated with a specific written form of its name in Kanji characters.
  • F. None of above.

Provenance (6 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_69e288c808b881909fed7d18f04bcbbe completed April 17, 2026, 7:23 p.m.
NER Named-entity recognition batch_69f1dee718f88190860d40c6f09a77c8 completed April 29, 2026, 10:35 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0f969177408190aaf66a4daeb25e52 completed May 21, 2026, 11:34 p.m.
NEDg Description generation batch_6a0f96e1bccc8190a270f490d167483d completed May 21, 2026, 11:36 p.m.
NED2 Entity disambiguation (via description) batch_6a0f98194640819086e65f85bb0bede1 completed May 21, 2026, 11:41 p.m.
PD Predicate disambiguation batch_69f1765650fc8190a6bc1eb512b240bf completed April 29, 2026, 3:09 a.m.
Created at: April 17, 2026, 11:06 p.m.