Triple
T16535845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tsurugizaki |
E401687
|
entity |
| Predicate | laterName |
P65
|
FINISHED |
| Object | Shōhō |
E48360
|
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: Shōhō | Statement: [Tsurugizaki, laterName, Shōhō]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Shōhō Context triple: [Tsurugizaki, laterName, Shōhō]
-
A.
Shōhō
Shōhō was a Japanese era name (nengō) of the early Edo period, used for a brief span in the mid-17th century.
-
B.
Shōhō
chosen
Shōhō was a Japanese light aircraft carrier of the Imperial Japanese Navy during World War II, notable for being the first Japanese carrier sunk in the war during the Battle of the Coral Sea.
-
C.
Shinpei
Shinpei is a Japanese given name commonly used for males and borne by various notable figures in politics, arts, and entertainment.
-
D.
Naoyoshi
Naoyoshi is a Japanese given name commonly used for males.
-
E.
Shōshi
Shōshi is the romanized name of Empress Shōshi, a Japanese imperial consort of the Heian period and a prominent cultural patron.
- 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_69d88384bc30819084229e7dcdc39a41 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e345574d88819094548367bf983078 |
completed | April 18, 2026, 8:48 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00dbf6507081909f6a49c003f9d6d6 |
completed | May 10, 2026, 7:26 p.m. |
Created at: April 10, 2026, 5:15 a.m.