Triple
T34383136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yun |
E882489
|
entity |
| Predicate | possibleHanja |
P27905
|
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: [Yun, possibleHanja, 尹]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: possibleHanja Context triple: [Yun, possibleHanja, 尹]
-
A.
hanjaName
chosen
Indicates that one entity is the Sino-Korean (hanja) written form corresponding to the name of another entity.
-
B.
usesHanjaVariants
Indicates that one entity employs or incorporates alternative Hanja (Chinese character) forms corresponding to another entity.
-
C.
kanji
Indicates that an entity is written in, represented by, or associated with a specific kanji character or set of kanji characters.
-
D.
possibleKanjiMeaning
Indicates that a given meaning is a possible or candidate interpretation associated with a particular kanji character.
-
E.
componentKanji2
Indicates that one kanji character serves as the second component or sub-part of another kanji.
- 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_69f349c0219881909393bbbc1edc8161 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7688dd3d08190ad13d0e780570a1c |
completed | May 3, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69f767fcf2f881908bacc7bfc38e68a5 |
completed | May 3, 2026, 3:21 p.m. |
Created at: May 1, 2026, 1:59 a.m.