Triple
T14023124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 九七式艦上攻撃機 |
E337385
|
entity |
| Predicate | countryOfOrigin |
P26
|
FINISHED |
| Object | 大日本帝国 |
E643007
|
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: [九七式艦上攻撃機, countryOfOrigin, 大日本帝国]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 大日本帝国 Context triple: [九七式艦上攻撃機, countryOfOrigin, 大日本帝国]
-
A.
大日本帝国
chosen
大日本帝国は、明治維新後から第二次世界大戦終結まで続いた、日本の天皇制を中心とする近代立憲君主国家である。
-
B.
Imperial Japan
Imperial Japan was the militaristic empire that dominated East Asia in the early 20th century and served as a principal Axis power in World War II, pursuing aggressive expansion and engaging in major conflicts with the Allied nations.
-
C.
大和
大和 is the historical Japanese name for the ancient province and cultural heartland that gave rise to the early Japanese state and imperial court.
-
D.
陸奥国
陸奥国 was an expansive historical province in northeastern Honshū, Japan, encompassing much of the modern Tōhoku region.
-
E.
Nippon Eitaigura
Nippon Eitaigura is a late 17th-century Japanese ukiyo-zōshi story collection by Ihara Saikaku that vividly portrays the lives and fortunes of Osaka merchants.
- 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_69d81c6543a48190bd5ba93d7419e797 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2f3d87b88190b038d334f4965369 |
completed | April 14, 2026, 12:12 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fbc33170ec8190b0ffe41a567a590b |
completed | May 6, 2026, 10:39 p.m. |
Created at: April 9, 2026, 10:19 p.m.