Triple
T2497339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Panther tank |
E52181
|
entity |
| Predicate | frontArmorThickness |
P39153
|
FINISHED |
| Object | up to 80 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 80 mm | Statement: [Panther tank, frontArmorThickness, up to 80 mm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frontArmorThickness Context triple: [Panther tank, frontArmorThickness, up to 80 mm]
-
A.
sideArmorThickness
Indicates the thickness of an object's armor specifically along its sides.
-
B.
frontHullArmorThickness
chosen
Indicates the thickness of the armor located on the front section of a vehicle’s hull.
-
C.
deckArmorThickness
Indicates the thickness of the armor plating on the horizontal deck surface of a vehicle, vessel, or structure.
-
D.
frontArmorRange
Indicates the range or extent of protective armor coverage on the front-facing side of an entity.
-
E.
armoredBeltThickness
Indicates the thickness of an entity’s protective armored belt in the context of its defensive structure or design.
- 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_69ab4955111c8190835bf619adec21ff |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd1ad2f8c81908853e97d75081e84 |
completed | March 7, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69abd0b980b481908d4932bcea4a6167 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:46 p.m.