Triple
T24876125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fletcher-class destroyer |
E622573
|
entity |
| Predicate | torpedoArmamentCount |
P63127
|
FINISHED |
| Object | 10 tubes in two quintuple mounts |
—
|
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: 10 tubes in two quintuple mounts | Statement: [Fletcher-class destroyer, torpedoArmamentCount, 10 tubes in two quintuple mounts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: torpedoArmamentCount Context triple: [Fletcher-class destroyer, torpedoArmamentCount, 10 tubes in two quintuple mounts]
-
A.
numberOfTorpedoTubes
chosen
Indicates the quantity of torpedo tubes associated with or installed on an entity.
-
B.
armamentTorpedoes
Indicates that an entity is equipped with torpedoes as part of its armament or weaponry.
-
C.
torpedoCaliber
Indicates the specific diameter or size classification of a torpedo used in a given context or system.
-
D.
numberOfTorpedoesFired
Indicates the quantity of torpedoes that have been launched or discharged in a given context or event.
-
E.
missileTubesPerBoat
Indicates the number of missile tubes associated with each individual boat in the relationship.
- 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_69e2fac3fdbc81909c2ec49be5743cd9 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f43043512481909501a3979cac9947 |
completed | May 1, 2026, 4:46 a.m. |
| PD | Predicate disambiguation | batch_69f420fd375c81908ea4a4e60b76ee8f |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:24 a.m.