Triple
T6061815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 南次郎 |
E135048
|
entity |
| Predicate | 肩書 |
P68413
|
FINISHED |
| Object | 朝鮮総督 |
E10246
|
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: 朝鮮総督 | Statement: [南次郎, 肩書, 朝鮮総督]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 朝鮮総督 Context triple: [南次郎, 肩書, 朝鮮総督]
-
A.
Resident-General of Korea
The Resident-General of Korea was the chief Japanese colonial official who oversaw Korea’s affairs during the protectorate period before its full annexation by Japan.
-
B.
韓国統監
韓国統監 refers to the Resident-General of Korea, the chief Japanese colonial administrator who exercised de facto control over Korea in the early 20th century prior to its formal annexation by Japan.
-
C.
朝鮮総督府
朝鮮総督府は、1910年の日韓併合以降に日本が朝鮮半島を統治するために設置した植民地統治機関である。
-
D.
Governor-General of Korea
chosen
The Governor-General of Korea was the top Japanese colonial authority that exercised military, political, and administrative control over Korea during its occupation from 1910 to 1945.
-
E.
Chief Executive of Manchukuo
The Chief Executive of Manchukuo was the head of state of the Japanese-controlled puppet regime established in northeastern China in the early 1930s.
- 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_69c00878d06881909ee78e88913bf890 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c0572100e8819084c3174921a2d527 |
completed | March 22, 2026, 8:54 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c11d1e61188190aea0e2b1945ca682 |
completed | March 23, 2026, 10:59 a.m. |
Created at: March 22, 2026, 4:10 p.m.