Triple
T4267012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kongō-class battlecruiser |
E96848
|
entity |
| Predicate | firstShipLaunched |
P34263
|
FINISHED |
| Object |
Japanese battlecruiser Kongō
Japanese battlecruiser Kongō was a World War I–era capital ship of the Imperial Japanese Navy that later served extensively in World War II after being modernized into a fast battleship.
|
E445466
|
NE FINISHED |
How this triple was built (5 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: Japanese battlecruiser Kongō | Statement: [Kongō-class battlecruiser, firstShipLaunched, Japanese battlecruiser Kongō]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Japanese battlecruiser Kongō Context triple: [Kongō-class battlecruiser, firstShipLaunched, Japanese battlecruiser Kongō]
-
A.
Japanese battlecruiser Haruna
The Japanese battlecruiser Haruna was an Imperial Japanese Navy capital ship that served prominently in both World War I and World War II, participating in major Pacific naval engagements before being sunk in 1945.
-
B.
Japanese battlecruiser Takao
Japanese battlecruiser Takao was a planned but never completed Amagi-class capital ship of the Imperial Japanese Navy intended to serve as a fast, heavily armed battlecruiser in the early 20th century.
-
C.
Japanese battlecruiser Kirishima
Japanese battlecruiser Kirishima was an Imperial Japanese Navy capital ship of World War II that fought in several major Pacific engagements before being sunk during the Naval Battle of Guadalcanal in 1942.
-
D.
Japanese battleship Mutsu
Japanese battleship Mutsu was a Nagato-class dreadnought of the Imperial Japanese Navy, notable for its powerful 16-inch guns and its accidental magazine explosion and sinking in 1943.
-
E.
Japanese battleship Mikasa
The Japanese battleship Mikasa was a pre-dreadnought battleship that served as Admiral Tōgō Heihachirō’s flagship and played a pivotal role in Japan’s naval victories during the Russo-Japanese War.
- 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: Japanese battlecruiser Kongō Triple: [Kongō-class battlecruiser, firstShipLaunched, Japanese battlecruiser Kongō]
Generated description
Japanese battlecruiser Kongō was a World War I–era capital ship of the Imperial Japanese Navy that later served extensively in World War II after being modernized into a fast battleship.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Japanese battlecruiser Kongō Target entity description: Japanese battlecruiser Kongō was a World War I–era capital ship of the Imperial Japanese Navy that later served extensively in World War II after being modernized into a fast battleship.
-
A.
Japanese battlecruiser Haruna
The Japanese battlecruiser Haruna was an Imperial Japanese Navy capital ship that served prominently in both World War I and World War II, participating in major Pacific naval engagements before being sunk in 1945.
-
B.
Japanese battlecruiser Takao
Japanese battlecruiser Takao was a planned but never completed Amagi-class capital ship of the Imperial Japanese Navy intended to serve as a fast, heavily armed battlecruiser in the early 20th century.
-
C.
Japanese battlecruiser Kirishima
Japanese battlecruiser Kirishima was an Imperial Japanese Navy capital ship of World War II that fought in several major Pacific engagements before being sunk during the Naval Battle of Guadalcanal in 1942.
-
D.
Japanese battleship Mutsu
Japanese battleship Mutsu was a Nagato-class dreadnought of the Imperial Japanese Navy, notable for its powerful 16-inch guns and its accidental magazine explosion and sinking in 1943.
-
E.
Japanese battleship Mikasa
The Japanese battleship Mikasa was a pre-dreadnought battleship that served as Admiral Tōgō Heihachirō’s flagship and played a pivotal role in Japan’s naval victories during the Russo-Japanese War.
- F. None of above. chosen
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstShipLaunched Context triple: [Kongō-class battlecruiser, firstShipLaunched, Japanese battlecruiser Kongō]
-
A.
originalShipLaunchedIn
Indicates that an original ship was first launched in a specified year, place, or context.
-
B.
firstShip
chosen
Indicates that the subject is the earliest or initial ship associated with, created by, or used in relation to the object.
-
C.
dateOfKeelLaying
Indicates the calendar date on which the keel of a vessel was formally laid, marking the official start of its construction.
-
D.
notableShip
Indicates that there is a notable or significant ship associated with the subject entity.
-
E.
firstCrewedFlightDate
Indicates the calendar date on which an entity undertook its first flight carrying human crew.
- F. None of above.
Provenance (6 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_69b34543f06c8190915ebb1a4574ffa9 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34fce710481909d90ed4a3d150fde |
completed | March 12, 2026, 11:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69badb1ba5d0819097382a689002cca5 |
completed | March 18, 2026, 5:04 p.m. |
| NEDg | Description generation | batch_69bb0abc3ec0819093b405374780d1c0 |
completed | March 18, 2026, 8:27 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69bb0b2ca62481909d9eb06f336a7996 |
completed | March 18, 2026, 8:29 p.m. |
| PD | Predicate disambiguation | batch_69b347f8dcb08190a725c1f7fb5a7466 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:07 p.m.