Triple
T19376401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ho |
E484678
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object |
Ho (Korean 호)
Ho (Korean 호) is a Korean given name or name element that can be represented by various hanja characters, each with its own meaning.
|
E1372772
|
NE FINISHED |
How this triple was built (4 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: Ho (Korean 호) | Statement: [Ho, hasVariant, Ho (Korean 호)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ho (Korean 호) Context triple: [Ho, hasVariant, Ho (Korean 호)]
-
A.
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.
-
B.
Seo (Korean surname)
Seo is a common Korean family name that can be romanized in various ways, including Suh, and is borne by numerous notable figures in Korean history and contemporary culture.
-
C.
In-hwoi
In-hwoi is the given name of Koo In-hwoi, the South Korean entrepreneur who founded the LG Group conglomerate.
-
D.
Heo
Heo is a Korean family name shared by various individuals, including contemporary public figures and historical lineages in Korea.
-
E.
Hyeonreung
Hyeonreung is a royal tomb from Korea’s Joseon Dynasty, notable as one of the UNESCO-listed burial sites of its kings and queens.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Ho (Korean 호) Triple: [Ho, hasVariant, Ho (Korean 호)]
Generated description
Ho (Korean 호) is a Korean given name or name element that can be represented by various hanja characters, each with its own meaning.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Ho (Korean 호) Target entity description: Ho (Korean 호) is a Korean given name or name element that can be represented by various hanja characters, each with its own meaning.
-
A.
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.
-
B.
Seo (Korean surname)
Seo is a common Korean family name that can be romanized in various ways, including Suh, and is borne by numerous notable figures in Korean history and contemporary culture.
-
C.
In-hwoi
In-hwoi is the given name of Koo In-hwoi, the South Korean entrepreneur who founded the LG Group conglomerate.
-
D.
Heo
Heo is a Korean family name shared by various individuals, including contemporary public figures and historical lineages in Korea.
-
E.
Hyeonreung
Hyeonreung is a royal tomb from Korea’s Joseon Dynasty, notable as one of the UNESCO-listed burial sites of its kings and queens.
- F. None of above. chosen
Provenance (5 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_69d8e8d460d88190abf0591c5c9d2b0c |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e61a5c05c08190b91cb32fdb79813b |
completed | April 20, 2026, 12:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a07241dfc208190896705ec6890b6f7 |
completed | May 15, 2026, 1:48 p.m. |
| NEDg | Description generation | batch_6a0724fd84988190a7eedab55f97bf84 |
completed | May 15, 2026, 1:51 p.m. |
| NED2 | Entity disambiguation (via description) | batch_6a0725d8da888190a94622b54d68d7c6 |
completed | May 15, 2026, 1:55 p.m. |
Created at: April 10, 2026, 1:35 p.m.