Triple
T13654897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lim |
E326832
|
entity |
| Predicate | writingSystem |
P454
|
FINISHED |
| Object | Hanja |
E139773
|
NE 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: Hanja | Statement: [Lim, writingSystem, Hanja]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hanja Context triple: [Lim, writingSystem, Hanja]
-
A.
Hanja
chosen
Hanja is the set of traditional Chinese characters historically used to write Korean, especially for proper names, academic terms, and classical texts.
-
B.
Hangul
Hangul is the native alphabetic writing system of the Korean language, renowned for its scientific design and ease of learning.
-
C.
Yi script
Yi script is a traditional logographic and syllabic writing system used to represent the Yi languages of southwestern China.
-
D.
Hangul Jamo
Hangul Jamo is a Unicode block that encodes the individual consonant and vowel letters used to write the Korean Hangul script.
-
E.
Hangul Syllables
Hangul Syllables is the Unicode block that encodes the precomposed modern Korean syllabic characters used for writing Hangul.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d8076d8270819092afc2f0e9c359a8 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc60ace048190a4b92310ba272bd1 |
completed | April 12, 2026, 4:19 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f78b03083c8190855a2a4ee44e4098 |
completed | May 3, 2026, 5:50 p.m. |
Created at: April 9, 2026, 9:52 p.m.