Triple
T15683762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Takao class |
E377643
|
entity |
| Predicate | designedMainBatteryCaliber |
P6076
|
FINISHED |
| Object | 203 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: 203 mm | Statement: [Takao class, designedMainBatteryCaliber, 203 mm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedMainBatteryCaliber Context triple: [Takao class, designedMainBatteryCaliber, 203 mm]
-
A.
gunCalibre
chosen
Indicates the relationship between a firearm and the calibre (size/diameter) of ammunition it is designed to use.
-
B.
numberOfMainBatteryGuns
Indicates the quantity of primary (main) battery guns that an entity, typically a warship or similar platform, is equipped with.
-
C.
ammunitionType
Indicates the specific kind or category of ammunition associated with or used by an entity.
-
D.
mainGunModel
Indicates the specific model or type designation of the primary gun or main weapon system used by an entity.
-
E.
plannedMainBatteryConfiguration
Indicates the intended or designed primary weapon or main battery setup that was planned for an entity, typically before implementation or construction.
- 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_69d85cd2e28481909d4e975bee20872f |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04f31b5b881908e46ecd9fc6048ab |
completed | April 16, 2026, 2:53 a.m. |
| PD | Predicate disambiguation | batch_69deda8c856c8190882330114f9a1a5f |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:17 a.m.