Triple
T22837390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heo |
E565983
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Hŏ (McCune–Reischauer) |
—
|
NE NERFINISHED |
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: Hŏ (McCune–Reischauer) | Statement: [Heo, hasVariant, Hŏ (McCune–Reischauer)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hŏ (McCune–Reischauer) Context triple: [Heo, hasVariant, Hŏ (McCune–Reischauer)]
-
A.
Ho (Korean 호)
chosen
Ho (Korean 호) is a Korean given name or name element that can be represented by various hanja characters, each with its own meaning.
-
B.
Munhwaŏ
Munhwaŏ is the standardized form of the Korean language used in North Korea, based primarily on the Pyongyang dialect.
-
C.
Hong (Korean surname)
Hong is a Korean family name of Chinese character origin, borne by numerous Koreans and associated with various historical and contemporary figures.
-
D.
Hyeol
Hyeol was the personal given name of King Seongjong, the ninth monarch of Korea’s Joseon dynasty.
-
E.
Sŏnjŏngnŭng
Sŏnjŏngnŭng is a historic royal tomb complex in Seoul, South Korea, housing the burial sites of Joseon Dynasty royalty and recognized as a UNESCO World Heritage Site.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e245869e188190a196584f36e682da |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17e303cec81909c5c118dc8c93354 |
completed | April 29, 2026, 3:42 a.m. |
Created at: April 17, 2026, 3:35 p.m.