Triple
T6775629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hobart-class destroyer |
E155146
|
entity |
| Predicate | hasTorpedo |
P13762
|
FINISHED |
| Object | lightweight anti-submarine torpedoes |
—
|
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: lightweight anti-submarine torpedoes | Statement: [Hobart-class destroyer, hasTorpedo, lightweight anti-submarine torpedoes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTorpedo Context triple: [Hobart-class destroyer, hasTorpedo, lightweight anti-submarine torpedoes]
-
A.
numberOfTorpedoesHit
Indicates the number of torpedoes that successfully struck a specified target.
-
B.
torpedoCaliber
Indicates the specific diameter or size classification of a torpedo used in a given context or system.
-
C.
numberOfTorpedoTubes
Indicates the quantity of torpedo tubes associated with or installed on an entity.
-
D.
armamentTorpedoes
chosen
Indicates that an entity is equipped with torpedoes as part of its armament or weaponry.
-
E.
dateHitByTorpedo
Indicates the specific date on which an entity was struck by a torpedo.
- 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_69c68812ef7c819099369f51febb725c |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d24f77c88190be21cf4ef132aa31 |
completed | March 27, 2026, 6:54 p.m. |
| PD | Predicate disambiguation | batch_69c6d094105881909c5806eb4afa6306 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:13 p.m.