Triple
T21273366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hwang In-ho |
E524323
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Hwang |
—
|
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: Hwang | Statement: [Hwang In-ho, familyName, Hwang]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hwang Context triple: [Hwang In-ho, familyName, Hwang]
-
A.
Hwang
chosen
Hwang is a surname most prominently associated with David Henry Hwang, the acclaimed American playwright known for works exploring Asian American identity and cross-cultural themes.
-
B.
In-hwoi
In-hwoi is the given name of Koo In-hwoi, the South Korean entrepreneur who founded the LG Group conglomerate.
-
C.
Chang-Gyu Hwang
Chang-Gyu Hwang is a South Korean business executive and technologist best known for his leadership roles at Samsung Electronics, particularly in advancing the semiconductor industry.
-
D.
Hwanung
Hwanung is a heavenly prince in Korean mythology who descends from the sky to found a sacred city and becomes the father of Dangun, the legendary founder of Gojoseon.
-
E.
Hwangje
Hwangje is the Korean imperial title corresponding to the Chinese sovereign known as the Yellow Emperor (Huangdi).
- 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_69e0b516293c819089458ea2ec85f85e |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e73655717c819092f71ed1920f52b5 |
completed | April 21, 2026, 8:33 a.m. |
Created at: April 16, 2026, 4:01 p.m.