Triple
T37850398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Japanese destroyer Akizuki |
E944034
|
entity |
| Predicate | armamentASW |
P20717
|
FINISHED |
| Object | depth charges |
—
|
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: depth charges | Statement: [Japanese destroyer Akizuki, armamentASW, depth charges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: armamentASW Context triple: [Japanese destroyer Akizuki, armamentASW, depth charges]
-
A.
antiSubmarineArmament
chosen
Indicates the type or presence of weapons or equipment specifically designed for anti-submarine warfare associated with an entity.
-
B.
armamentAsCarrier
Indicates that one entity serves as a carrier or delivery platform for another entity used as an armament or weapon.
-
C.
armamentAsBuilt
Indicates the weaponry or armament configuration that an object (such as a vehicle, vessel, or structure) originally had when it was first constructed or completed.
-
D.
aircraftArmament
Indicates that an aircraft is equipped with a particular weapon or armament system.
-
E.
tertiaryArmament
Indicates the relationship where an entity possesses or is equipped with a third-level (tertiary) weapon or armament beyond its primary and secondary armaments.
- 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_69f76eed4d9c81908b1b71ba9e3b61fe |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc995dc2481908b3bd4217f8101e7 |
completed | May 6, 2026, 11:07 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ee04f08190977b7ad70fc85896 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:19 p.m.