Triple
T32750716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AMX-30B |
E837486
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | AMX-30 variant |
C25956
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: AMX-30 variant Context triple: [AMX-30B, instanceOf, AMX-30 variant]
-
A.
Dassault Mirage III variant
A Dassault Mirage III variant is a specific model within the Mirage III family of French supersonic jet fighters, distinguished by tailored modifications in avionics, engines, armament, or mission role to meet particular operational or export requirements.
-
B.
third-generation tank
chosen
A third-generation tank is a modern main battle tank characterized by advanced composite armor, powerful smoothbore guns, sophisticated fire-control systems, and enhanced mobility designed for high-intensity, combined-arms warfare.
-
C.
Humvee variant
A Humvee variant is a specific configuration of the High Mobility Multipurpose Wheeled Vehicle (HMMWV) tailored with distinct equipment, armor, or mission-specific modifications to fulfill particular operational roles.
-
D.
Karl-Gerät
Karl-Gerät was a series of German World War II self-propelled siege mortars, among the largest artillery pieces ever built, designed to fire massive shells against heavily fortified targets.
-
E.
self-propelled howitzer variant
A self-propelled howitzer variant is an armored, mobile artillery platform built on a powered chassis that modifies a base howitzer design for specific roles such as increased firepower, protection, mobility, or specialized mission capabilities.
- F. None of above.
Provenance (1 batch)
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_69f34937f97c8190b7f84bea045df3ae |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:12 a.m.