Triple
T9610583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jeong |
E232087
|
entity |
| Predicate | hasAlternativeTransliteration |
P5923
|
FINISHED |
| Object | Chŏng |
E321784
|
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: Chŏng | Statement: [Jeong, hasAlternativeTransliteration, Chŏng]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Chŏng Context triple: [Jeong, hasAlternativeTransliteration, Chŏng]
-
A.
Cheong
chosen
Cheong is a variant transliteration of the Chinese surname commonly romanized as Zhang, used in certain dialects and regional naming conventions.
-
B.
Koung-Khi
Koung-Khi is an administrative department located in the West Region of Cameroon.
-
C.
Yeoncheon
Yeoncheon is a county in Gyeonggi Province, South Korea, known for its location near the Demilitarized Zone (DMZ) and its significant historical and military sites.
-
D.
Myeong-bok
Myeong-bok is the given name of Gojong, the 26th king of the Joseon dynasty and first emperor of the Korean Empire.
-
E.
Chongra
Chongra is a small settlement located in Pakistan’s Astore Valley in the Gilgit-Baltistan region of the Himalayas.
- 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_69ca8485a90c819094fe40b42fde9d70 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9a85d4c881909ccab2e972d97e68 |
completed | April 1, 2026, 10:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d179513f9081909bcd9a456c640ba3 |
completed | April 4, 2026, 8:49 p.m. |
Created at: March 30, 2026, 8:08 p.m.