Triple
T30721653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I-19 |
E782169
|
entity |
| Predicate | torpedoSpread |
P96322
|
FINISHED |
| Object | six torpedoes in single salvo against USS Wasp task force |
—
|
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: six torpedoes in single salvo against USS Wasp task force | Statement: [I-19, torpedoSpread, six torpedoes in single salvo against USS Wasp task force]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: torpedoSpread Context triple: [I-19, torpedoSpread, six torpedoes in single salvo against USS Wasp task force]
-
A.
torpedoCaliber
Indicates the specific diameter or size classification of a torpedo used in a given context or system.
-
B.
torpedoDamageEffect
Indicates the effect or impact that a torpedo’s damage has on its target.
-
C.
numberOfTorpedoesFired
chosen
Indicates the quantity of torpedoes that have been launched or discharged in a given context or event.
-
D.
armamentTorpedoes
Indicates that an entity is equipped with torpedoes as part of its armament or weaponry.
-
E.
numberOfTorpedoTubes
Indicates the quantity of torpedo tubes associated with or installed on an 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_69f224acd24481908ed5f96f0d69b5dd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f68c5a08648190af6e1d9a99876410 |
completed | May 2, 2026, 11:44 p.m. |
| PD | Predicate disambiguation | batch_69f6861170d08190bb98be609d436f84 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:36 p.m.