Triple
T9765471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mobile Fleet |
E236977
|
entity |
| Predicate | notableShip |
P3345
|
FINISHED |
| Object | Taihō |
E259440
|
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: Taihō | Statement: [Mobile Fleet, notableShip, Taihō]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Taihō Context triple: [Mobile Fleet, notableShip, Taihō]
-
A.
Taiho
chosen
Taiho was a Japanese Imperial Navy aircraft carrier of World War II, notable as Japan’s first fully armored carrier and for its brief service before sinking in the Battle of the Philippine Sea.
-
B.
Hōshō
Hōshō was the Imperial Japanese Navy’s pioneering aircraft carrier and the world’s first purpose-built carrier to enter service.
-
C.
Keihō
Keihō is the primary criminal law code of Japan that defines offenses and their penalties.
-
D.
Taihoku
Taihoku was the Japanese colonial-era name for Taipei, which served as the administrative and political center of Taiwan under Japanese rule.
-
E.
Hakutaka
Hakutaka is a high-speed train service operating on Japan’s Hokuriku Shinkansen line, connecting Tokyo with cities along the Sea of Japan coast.
- 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_69ca84d831b8819090322686b47887ce |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda0a040988190b1c940f9e5c42f9c |
completed | April 1, 2026, 10:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d1bcf965e88190b505ce160f77e9b7 |
completed | April 5, 2026, 1:38 a.m. |
Created at: March 30, 2026, 8:25 p.m.