Triple
T5329792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Izumo-class helicopter destroyer |
E123275
|
entity |
| Predicate | hasHullDesignFeature |
P6684
|
FINISHED |
| Object | starboard-side island superstructure |
—
|
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: starboard-side island superstructure | Statement: [Izumo-class helicopter destroyer, hasHullDesignFeature, starboard-side island superstructure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHullDesignFeature Context triple: [Izumo-class helicopter destroyer, hasHullDesignFeature, starboard-side island superstructure]
-
A.
hasHullType
Indicates that an entity possesses or is characterized by a specific type or form of hull.
-
B.
hasArchitecturalFeature
chosen
Indicates that one entity possesses, includes, or is characterized by a specific architectural feature or element.
-
C.
hasBodyPlanFeature
Indicates that an organism’s body plan includes a specific structural or morphological feature.
-
D.
hasDesignOption
Indicates that an entity is associated with or offers a particular design alternative or configurable design choice.
-
E.
hasMountingFeature
Indicates that one entity includes or provides a structural feature intended for mounting or attaching another entity.
- 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_69bd46477f9081909d242a327d749466 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd859552d8819080758bdd7c43c66a |
completed | March 20, 2026, 5:36 p.m. |
| PD | Predicate disambiguation | batch_69bd84583dbc819088a03e3afb30178c |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2 p.m.