Triple

T4410817
Position Surface form Disambiguated ID Type / Status
Subject Jung E94848 entity
Predicate hasScript P182 FINISHED
Object Hangul E25453 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: Hangul | Statement: [Jung, hasScript, Hangul]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hangul
Context triple: [Jung, hasScript, Hangul]
  • A. Hangul chosen
    Hangul is the native alphabetic writing system of the Korean language, renowned for its scientific design and ease of learning.
  • B. Hanja
    Hanja is the set of traditional Chinese characters historically used to write Korean, especially for proper names, academic terms, and classical texts.
  • C. Korean
    Korean is an East Asian language spoken primarily in both North and South Korea, known for its unique Hangul writing system and distinct linguistic structure.
  • D. Baeggu language
    The Baeggu language is an Oceanic language spoken by the Baeggu people in the Solomon Islands, belonging to the Southeast Solomonic branch of the Austronesian language family.
  • E. Hangul Jamo Extended-A
    Hangul Jamo Extended-A is a Unicode block that contains additional archaic and extended Hangul jamo characters used for representing Old Korean and specialized orthographic forms.
  • 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_69b34539638c8190abfea3eb29425210 completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b354e4c58c8190b4190aad3095a1dd completed March 13, 2026, 12:05 a.m.
NED1 Entity disambiguation (via context triple) batch_69b5f60ea0808190a59418f7911d123d completed March 14, 2026, 11:58 p.m.
Created at: March 12, 2026, 11:29 p.m.