Triple
T29263289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Assault Amphibious Vehicle |
E741908
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | amphibious armored personnel carrier |
C15396
|
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: amphibious armored personnel carrier Context triple: [Assault Amphibious Vehicle, instanceOf, amphibious armored personnel carrier]
-
A.
amphibious vehicle
An amphibious vehicle is a transport vehicle designed to operate efficiently on both land and water by seamlessly transitioning between driving and floating or sailing modes.
-
B.
amphibious warfare vessel class
An amphibious warfare vessel class is a group of naval ships designed and equipped to project ground forces from sea to shore, typically carrying troops, vehicles, and landing craft while providing command, control, and logistical support for amphibious operations.
-
C.
armored utility vehicle
An armored utility vehicle is a heavily protected, multi-purpose transport platform designed to safely carry personnel, equipment, or cargo through hazardous or combat-prone environments.
-
D.
armored military vehicle
chosen
An armored military vehicle is a heavily protected, often weaponized, ground transport designed to carry personnel or equipment safely through hostile environments.
-
E.
armoured fighting vehicle
An armoured fighting vehicle is a heavily protected, mobile combat platform—typically tracked or wheeled—designed to engage enemy forces using integrated weapons systems on the battlefield.
- 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_69f0912065c08190bddd23e20e8ef18e |
completed | April 28, 2026, 10:51 a.m. |
Created at: April 28, 2026, 12:43 p.m.