Triple
T16254847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tokyo Express |
E394601
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Allied military nickname |
C31522
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Allied military nickname Context triple: [Tokyo Express, instanceOf, Allied military nickname]
-
A.
U.S. military call sign
A U.S. military call sign is a standardized, often coded identifier used in voice and data communications to uniquely designate units, aircraft, ships, or personnel while enhancing operational clarity and security.
-
B.
military aircraft nickname
A military aircraft nickname is an informal or semi-official moniker given to a specific aircraft model or type, often reflecting its appearance, role, performance, or reputation among service members and the public.
-
C.
NATO reporting name
A NATO reporting name is a standardized code word or phrase assigned by NATO to identify and refer to military equipment, particularly aircraft and missiles from non-NATO countries, for clear and consistent communication.
-
D.
naval nickname
chosen
A naval nickname is an informal, often humorous or affectionate moniker given to a ship, sailor, unit, or naval organization that reflects its reputation, characteristics, or history.
-
E.
regimental nickname
A regimental nickname is an informal, often traditional or honorific name used to identify and distinguish a military regiment from others.
- F. None of above.
Provenance (1 batch)
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_69d87f2171208190951025e526947816 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 10, 2026, 5:04 a.m.