Triple
T21685268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 朝鮮総督府 |
E535213
|
entity |
| Predicate | 別名 |
P39
|
FINISHED |
| Object | 朝鮮総督府政庁 |
—
|
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: 朝鮮総督府政庁 | Statement: [朝鮮総督府, 別名, 朝鮮総督府政庁]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 朝鮮総督府政庁 Context triple: [朝鮮総督府, 別名, 朝鮮総督府政庁]
-
A.
朝鮮総督府
chosen
朝鮮総督府は、1910年の日韓併合以降に日本が朝鮮半島を統治するために設置した植民地統治機関である。
-
B.
Japanese Resident-General’s Office
The Japanese Resident-General’s Office was the colonial administrative authority established by Japan to oversee and control Korea prior to its formal annexation.
-
C.
Ministry of War of Joseon
The Ministry of War of Joseon was the central military administration of the Joseon Dynasty, responsible for overseeing the kingdom’s armed forces, defense policies, and military affairs.
-
D.
Pusanjin-gu Office
Pusanjin-gu Office is the local government administrative headquarters responsible for managing public services and municipal affairs in Pusanjin District of Busan, South Korea.
-
E.
Kwantung Government-General
The Kwantung Government-General was the Japanese colonial administration that governed the Kwantung Leased Territory in northeastern China during the early 20th century.
- 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_69e0c469b6ec8190aee4cadd1527db91 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef96ca668481909f53853c7a8ea811 |
completed | April 27, 2026, 5:03 p.m. |
Created at: April 16, 2026, 6:44 p.m.