Triple
T12420227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kŭmchŏng-gu |
E296748
|
entity |
| Predicate | usesHyphenBetweenSyllables |
P64072
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Kŭmchŏng-gu, usesHyphenBetweenSyllables, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesHyphenBetweenSyllables Context triple: [Kŭmchŏng-gu, usesHyphenBetweenSyllables, true]
-
A.
usesSyllables
Indicates that one entity forms, expresses, or analyzes something by employing syllables as its basic units.
-
B.
hasHyphenation
chosen
Indicates that one entity specifies or provides the hyphenated form or hyphenation pattern of another entity.
-
C.
hasSyllabicStructure
Indicates that an entity possesses a specific arrangement or pattern of syllables, such as their number, order, or type.
-
D.
hasSyllabary
Indicates that one entity possesses or is associated with a specific syllabary writing system used to represent its language or notation.
-
E.
usesFixedSpellingsForCommonSyllables
Indicates that an entity consistently applies predetermined, standard spellings for frequently occurring syllables.
- 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_69d6ada0640c81908c061d7fb3d47786 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94e1888b48190bd750f839a26e99e |
completed | April 10, 2026, 7:23 p.m. |
| PD | Predicate disambiguation | batch_69d94d354b488190adc83fb4f2770dd5 |
completed | April 10, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:55 p.m.