Triple

T1104408
Position Surface form Disambiguated ID Type / Status
Subject Hangul E25453 entity
Predicate syllableStructure P19239 FINISHED
Object block-like syllable clusters 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: block-like syllable clusters | Statement: [Hangul, syllableStructure, block-like syllable clusters]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: syllableStructure
Context triple: [Hangul, syllableStructure, block-like syllable clusters]
  • A. hasSyllableStructure chosen
    Indicates that an entity (typically a word or morpheme) possesses a particular arrangement or pattern of syllables.
  • B. hasSyllabicStructure
    Indicates that an entity possesses a specific arrangement or pattern of syllables, such as their number, order, or type.
  • C. hasSyllableCount
    Indicates that one entity (typically a word or phrase) possesses a specific number of syllables given by the other entity.
  • D. hasStressPattern
    Indicates that an entity (such as a word or phrase) follows a particular arrangement of stressed and unstressed units (e.g., syllables) in its pronunciation.
  • E. hasSyllabary
    Indicates that one entity possesses or is associated with a specific syllabary writing system used to represent its language or notation.
  • 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_69a49428d4448190b3b36991ceae87ce completed March 1, 2026, 7:31 p.m.
NER Named-entity recognition batch_69a4b9e1047481909af1cf8df2a01fff completed March 1, 2026, 10:12 p.m.
PD Predicate disambiguation batch_69a4b7472c848190b0643872f67084a2 completed March 1, 2026, 10:01 p.m.
Created at: March 1, 2026, 7:43 p.m.