Triple
T15891493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Panzerjäger I |
E385333
|
entity |
| Predicate | hullArmorMaterial |
P96342
|
FINISHED |
| Object | rolled homogeneous armor |
—
|
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: rolled homogeneous armor | Statement: [Panzerjäger I, hullArmorMaterial, rolled homogeneous armor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hullArmorMaterial Context triple: [Panzerjäger I, hullArmorMaterial, rolled homogeneous armor]
-
A.
armorMaterial
chosen
Indicates that one entity serves as the material or substance from which another entity’s armor is made.
-
B.
shieldMaterial
Indicates the material from which a shield is made or constructed.
-
C.
pressureHullMaterial
Indicates that one entity is the material from which the pressure hull of another entity is constructed.
-
D.
hullReinforcement
Indicates that an entity strengthens or protects the outer structure or hull of another entity, typically to increase its durability or resistance to damage.
-
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_69d86da5b800819083a31be937d738b0 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e17d4d08f481909f38b75e3f42d9ab |
completed | April 17, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69e142ca3b208190946c3aa4c1e6087c |
completed | April 16, 2026, 8:12 p.m. |
Created at: April 10, 2026, 4:51 a.m.