Triple
T1104404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hangul |
E25453
|
entity |
| Predicate | hasJamoType |
P16116
|
FINISHED |
| Object | choseong (initial consonant) |
—
|
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: choseong (initial consonant) | Statement: [Hangul, hasJamoType, choseong (initial consonant)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasJamoType Context triple: [Hangul, hasJamoType, choseong (initial consonant)]
-
A.
hasTypicalCharacterType
Indicates that an entity is commonly associated with or exemplified by a particular type of character or persona.
-
B.
hasCombiningMarks
Indicates that an entity (such as a character or string) includes one or more combining marks attached to a base element.
-
C.
hasSyllabary
Indicates that one entity possesses or is associated with a specific syllabary writing system used to represent its language or notation.
-
D.
hasConsonantSigns
chosen
Indicates that one entity possesses or includes consonant sign characters as part of its representation or structure.
-
E.
hasPhonologicalType
Indicates that one entity is characterized by or classified as having a particular phonological type (e.g., in terms of sound structure or phonological category).
- 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.