Triple
T16291149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 関東州 |
E395524
|
entity |
| Predicate | 別名 |
P39
|
FINISHED |
| Object | 関東租借地 |
E92452
|
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.
関東州
関東州は、20世紀前半に日本が中国東北部の遼東半島南部を租借して設置した植民地的統治区域を指す名称である。
-
B.
Kwantung Leased Territory
chosen
The Kwantung Leased Territory was a strategically important area in southern Manchuria controlled by Imperial Japan in the early 20th century, serving as a key military and colonial foothold on the Asian mainland.
-
C.
樺太庁
樺太庁 was the Japanese colonial government that administered the southern part of Sakhalin Island (Karafuto) under the Empire of Japan until the end of World War II.
-
D.
Nankai region
The Nankai region is a seismically active coastal area of southwestern Japan along the Nankai Trough, known for recurring large megathrust earthquakes and tsunamis.
-
E.
Taihoku Prefecture
Taihoku Prefecture was an administrative division of Japanese-ruled Taiwan, centered on present-day Taipei and surrounding areas, during the period of Japanese colonial governance.
- 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_69d87f22c7248190a54c949738441e2e |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2491821d0819086cffdd7551ba85a |
completed | April 17, 2026, 2:52 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a001f97895081909f22ded3507afe14 |
completed | May 10, 2026, 6:03 a.m. |
Created at: April 10, 2026, 5:05 a.m.