Triple

T19376402
Position Surface form Disambiguated ID Type / Status
Subject Ho E484678 entity
Predicate hasKoreanHangul P52969 FINISHED
Object LITERAL 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: 호 | Statement: [Ho, hasKoreanHangul, 호]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasKoreanHangul
Context triple: [Ho, hasKoreanHangul, 호]
  • A. koreanReadingHangul chosen
    Indicates that an entity’s Korean reading is represented in Hangul script.
  • B. hasKoreanVersion
    Indicates that something has a corresponding version or counterpart that is in the Korean language.
  • C. hasHakkaRomanization
    Indicates that an entity is associated with a specific representation of its name or term in Hakka Romanization.
  • D. hasMultipleChineseCharacters
    Indicates that the referenced item consists of more than one Chinese character.
  • E. hangulNameRomanized
    Indicates that an entity’s Korean Hangul name is represented in its romanized (Latin alphabet) form.
  • F. None of above.

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_69d8e8d460d88190abf0591c5c9d2b0c completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e61a5c05c08190b91cb32fdb79813b completed April 20, 2026, 12:21 p.m.
PD Predicate disambiguation batch_69e4fd54f8e48190956e73dd8969164a completed April 19, 2026, 4:05 p.m.
Created at: April 10, 2026, 1:35 p.m.