Triple
T9812557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hatsuzuki |
E238308
|
entity |
| Predicate | sunkAsResultOf |
P4687
|
FINISHED |
| Object | naval gunfire |
—
|
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: naval gunfire | Statement: [Hatsuzuki, sunkAsResultOf, naval gunfire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sunkAsResultOf Context triple: [Hatsuzuki, sunkAsResultOf, naval gunfire]
-
A.
sunkBy
chosen
Indicates that one entity (typically a vessel or structure) was caused to sink or be destroyed in water by another entity.
-
B.
sunkDuring
Indicates that one entity was sunk in the course of, or as a result of, the event or time period represented by another entity.
-
C.
sankOn
Indicates that one entity moved downward and became submerged or lower in level relative to another entity or reference point.
-
D.
torpedoed
Indicates that one entity attacked and struck another entity using a torpedo, typically causing damage or destruction.
-
E.
sunkAsTarget
Indicates that an entity was sunk specifically in the role of being a target (e.g., during testing, training, or as a deliberate target in an operation).
- 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_69ca84defac48190abc1148804f184c1 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb222ba788190a9085272a3de7852 |
completed | April 2, 2026, 12:02 a.m. |
| PD | Predicate disambiguation | batch_69cd03e01ea881909a7d93fc3994ace5 |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:30 p.m.