Triple
T21466818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 堀越 二郎 |
E529613
|
entity |
| Predicate | designed |
P184
|
FINISHED |
| Object | 三菱 J2M 雷電 |
E205562
|
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: 三菱 J2M 雷電 | Statement: [堀越 二郎, designed, 三菱 J2M 雷電]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 三菱 J2M 雷電 Context triple: [堀越 二郎, designed, 三菱 J2M 雷電]
-
A.
九七式艦上攻撃機
九七式艦上攻撃機は、第二次世界大戦期の日本海軍を代表する艦上攻撃機で、真珠湾攻撃などで主力として用いられた機体である。
-
B.
Mitsubishi J2M
chosen
The Mitsubishi J2M was a World War II Japanese land-based interceptor fighter designed for high-speed, high-altitude defense against enemy bombers.
-
C.
Mitsubishi J8M
The Mitsubishi J8M was a Japanese World War II rocket-powered interceptor aircraft, developed as a counterpart to Germany’s Messerschmitt Me 163 Komet.
-
D.
Mitsubishi A7M Reppū
The Mitsubishi A7M Reppū was an advanced Japanese carrier-based fighter aircraft developed in World War II as the intended successor to the famed A6M Zero.
-
E.
Nakajima A6M2-N
The Nakajima A6M2-N was a World War II Japanese single-float seaplane fighter derived from the Mitsubishi A6M Zero and used primarily for maritime patrol and air defense from remote island bases.
- 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_69e0c458133481908ae8b41a12c4edec |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9e9f32b5c8190bfa5acb3c9b1ab3b |
completed | April 23, 2026, 9:44 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a09cff53c5c8190824b561ed79da378 |
completed | May 17, 2026, 2:25 p.m. |
Created at: April 16, 2026, 6:13 p.m.