Triple
T21262933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M15/42 medium tank |
E524049
|
entity |
| Predicate | maximumArmorThickness |
P45211
|
FINISHED |
| Object | 42 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: 42 mm | Statement: [M15/42 medium tank, maximumArmorThickness, 42 mm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumArmorThickness Context triple: [M15/42 medium tank, maximumArmorThickness, 42 mm]
-
A.
armourThickness
Indicates the measured thickness of an entity’s protective armor in the context of defense or shielding.
-
B.
armourThicknessMin
Indicates the minimum measured or specified thickness of an object's armor in the described context.
-
C.
armorThicknessMax
chosen
Indicates the maximum thickness of armor that an entity possesses or can withstand.
-
D.
deckArmorThickness
Indicates the thickness of the armor plating on the horizontal deck surface of a vehicle, vessel, or structure.
-
E.
sideArmorThickness
Indicates the thickness of an object's armor specifically along its sides.
- 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_69e0b5156d7881909bd4f83676590715 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e735e9b2788190b834ba38367fb6c7 |
completed | April 21, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69e5f61239708190ab7b3c83ae848a0d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 4 p.m.