Triple
T33988290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Admiral Hipper-class heavy cruiser |
E871470
|
entity |
| Predicate | designedTurretFaceArmorThickness |
P187617
|
FINISHED |
| Object | up to 160 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: up to 160 mm | Statement: [Admiral Hipper-class heavy cruiser, designedTurretFaceArmorThickness, up to 160 mm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedTurretFaceArmorThickness Context triple: [Admiral Hipper-class heavy cruiser, designedTurretFaceArmorThickness, up to 160 mm]
-
A.
armorTurretFaceThickness
Indicates the thickness of the armor on the front-facing surface of a turret.
-
B.
turretRoofArmorThickness
Indicates the thickness of the armor on the roof section of a turret.
-
C.
turretFrontArmor_mm
chosen
Indicates the thickness, measured in millimeters, of the armor on the front face of a turret.
-
D.
turretRearArmorThickness
Indicates the thickness of the armor located at the rear section of a turret.
-
E.
armourThickness
Indicates the measured thickness of an entity’s protective armor in the context of defense or shielding.
- 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_69f3499e964c8190b674b03f6f791b4b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fecd0a732c819097bdd3eb69b6158c |
completed | May 9, 2026, 5:58 a.m. |
| PD | Predicate disambiguation | batch_69fecc0318d481908b5b20598a76a9fe |
completed | May 9, 2026, 5:54 a.m. |
Created at: May 1, 2026, 1:50 a.m.