Triple
T2336557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hiryū |
E44322
|
entity |
| Predicate | navalDesignationSystem |
P27155
|
FINISHED |
| Object | IJN internal hull number system |
—
|
LITERAL 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: IJN internal hull number system | Statement: [Hiryū, navalDesignationSystem, IJN internal hull number system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navalDesignationSystem Context triple: [Hiryū, navalDesignationSystem, IJN internal hull number system]
-
A.
USNDesignation
Indicates the formal designation assigned by the United States Navy to identify and classify a ship, aircraft, or other naval asset.
-
B.
navalStandardType
chosen
Indicates the specific naval standard or classification system under which an entity (such as a vessel, equipment, or procedure) is defined or regulated.
-
C.
airForceDesignation
Indicates that one entity is the official designation or code assigned to something by an air force.
-
D.
hasMilitaryDesignation
Indicates that an entity is assigned a specific military-related code, title, or classification.
-
E.
navalForceComposition
Indicates the makeup and distribution of different types of naval units or vessels within a particular naval force.
- F. None of above.
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_69a889132b488190bbb43ad4780ddd92 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abc6f75d888190a2e41edaa532e83f |
completed | March 7, 2026, 6:34 a.m. |
| PD | Predicate disambiguation | batch_69abc594087c819098100a10c5478a4b |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:51 p.m.