Triple
T14023155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 九七式艦上攻撃機 |
E337385
|
entity |
| Predicate | usedBy |
P260
|
FINISHED |
| Object |
空母加賀
空母加賀は、日本海軍が運用した代表的な正規空母の一つで、真珠湾攻撃など太平洋戦争初期の主要作戦に参加した艦船である。
|
E1075213
|
NE FINISHED |
How this triple was built (4 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: [九七式艦上攻撃機, usedBy, 空母加賀]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 空母加賀 Context triple: [九七式艦上攻撃機, usedBy, 空母加賀]
-
A.
空母「赤城」
空母「赤城」は、日本海軍を代表する大型正規空母の一つであり、真珠湾攻撃など太平洋戦争初期の主要作戦に参加した艦である。
-
B.
Japanese aircraft carrier Hiryū
The Japanese aircraft carrier Hiryū was a fleet carrier of the Imperial Japanese Navy that played a major role in early Pacific War operations before being sunk at the Battle of Midway in 1942.
-
C.
Japanese carrier Shokaku
Japanese carrier Shokaku was a major Imperial Japanese Navy fleet aircraft carrier, renowned for its role in early Pacific War battles before being sunk in 1944.
-
D.
Unryū-class aircraft carrier
The Unryū-class aircraft carrier was a World War II-era class of Japanese Imperial Navy fleet carriers designed as a simplified, faster-to-build successor to earlier carriers like the Hiryū.
-
E.
Kaga-class aircraft carrier
The Kaga-class aircraft carrier was a planned class of Japanese aircraft carriers derived from the Izumo-class helicopter destroyers, intended to operate fixed-wing STOVL jets like the F-35B.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: 空母加賀 Triple: [九七式艦上攻撃機, usedBy, 空母加賀]
Generated description
空母加賀は、日本海軍が運用した代表的な正規空母の一つで、真珠湾攻撃など太平洋戦争初期の主要作戦に参加した艦船である。
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: 空母加賀 Target entity description: 空母加賀は、日本海軍が運用した代表的な正規空母の一つで、真珠湾攻撃など太平洋戦争初期の主要作戦に参加した艦船である。
-
A.
空母「赤城」
空母「赤城」は、日本海軍を代表する大型正規空母の一つであり、真珠湾攻撃など太平洋戦争初期の主要作戦に参加した艦である。
-
B.
Japanese aircraft carrier Hiryū
The Japanese aircraft carrier Hiryū was a fleet carrier of the Imperial Japanese Navy that played a major role in early Pacific War operations before being sunk at the Battle of Midway in 1942.
-
C.
Japanese carrier Shokaku
Japanese carrier Shokaku was a major Imperial Japanese Navy fleet aircraft carrier, renowned for its role in early Pacific War battles before being sunk in 1944.
-
D.
Unryū-class aircraft carrier
The Unryū-class aircraft carrier was a World War II-era class of Japanese Imperial Navy fleet carriers designed as a simplified, faster-to-build successor to earlier carriers like the Hiryū.
-
E.
Kaga-class aircraft carrier
The Kaga-class aircraft carrier was a planned class of Japanese aircraft carriers derived from the Izumo-class helicopter destroyers, intended to operate fixed-wing STOVL jets like the F-35B.
- F. None of above. chosen
Provenance (5 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. |
| NEDg | Description generation | batch_69fbc6d1048081908fb2e798cbc9902f |
completed | May 6, 2026, 10:55 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69fbc76610008190bd3c7f357666c8db |
completed | May 6, 2026, 10:57 p.m. |
Created at: April 9, 2026, 10:19 p.m.