Triple
T17579891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paik Sun-yup |
E428173
|
entity |
| Predicate | name |
P16
|
FINISHED |
| Object | Paik Sun-yup |
—
|
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: Paik Sun-yup | Statement: [Paik Sun-yup, name, Paik Sun-yup]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Paik Sun-yup Context triple: [Paik Sun-yup, name, Paik Sun-yup]
-
A.
Paik Sun-yup
chosen
Paik Sun-yup was a South Korean army general renowned for his pivotal leadership during the Korean War and for helping to modernize South Korea’s armed forces.
-
B.
Chung Ju-yung
Chung Ju-yung was a South Korean entrepreneur and industrialist who built the Hyundai conglomerate into one of the country’s largest and most influential business empires.
-
C.
Jung Jang-seon
Jung Jang-seon is a South Korean politician serving as the mayor of the city of Pyeongtaek.
-
D.
Won In-choul
Won In-choul is a South Korean Air Force general who served as the country’s Chairman of the Joint Chiefs of Staff.
-
E.
Suh Yun-bok
Suh Yun-bok was a South Korean long-distance runner best known for winning the 1947 Boston Marathon and later serving as a symbolic sports figure in Korea.
- 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_69d889e1030481909950e140c63255b9 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e463cc493c8190965680cf786aa531 |
completed | April 19, 2026, 5:10 a.m. |
Created at: April 10, 2026, 5:50 a.m.