Triple
T31225573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Dreadnought |
E796123
|
entity |
| Predicate | gunCaliberMainBattery |
P118288
|
FINISHED |
| Object | 12-inch (305 mm) |
—
|
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: 12-inch (305 mm) | Statement: [HMS Dreadnought, gunCaliberMainBattery, 12-inch (305 mm)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gunCaliberMainBattery Context triple: [HMS Dreadnought, gunCaliberMainBattery, 12-inch (305 mm)]
-
A.
numberOfMainBatteryGuns
Indicates the quantity of primary (main) battery guns that an entity, typically a warship or similar platform, is equipped with.
-
B.
gunCalibre
Indicates the relationship between a firearm and the calibre (size/diameter) of ammunition it is designed to use.
-
C.
mainGunModel
Indicates the specific model or type designation of the primary gun or main weapon system used by an entity.
-
D.
primaryArmament
Indicates the main weapon or principal offensive system that an entity (such as a vehicle, vessel, or platform) is equipped with or uses.
-
E.
hasArtilleryCaliber
chosen
Indicates that an artillery piece is characterized by or equipped with a specific caliber (diameter) of its gun barrel or ammunition.
- 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_69f224da98f88190ab32f690cce5d303 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c50f4b481909d205c0a9807935e |
completed | May 3, 2026, 12:52 a.m. |
| PD | Predicate disambiguation | batch_69f696673214819094350e1d2648ef34 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:10 p.m.