Triple
T828599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ajax armoured fighting vehicle |
E17912
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | tracked reconnaissance vehicle |
C1743
|
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: tracked reconnaissance vehicle Context triple: [Ajax armoured fighting vehicle, instanceOf, tracked reconnaissance vehicle]
-
A.
armoured fighting vehicle
chosen
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.
-
B.
armored fighting vehicle
An armored fighting vehicle is a heavily protected, mobile combat platform designed to engage enemy forces using integrated weapon systems on land.
-
C.
infantry fighting vehicle
An infantry fighting vehicle is a heavily armed and armored combat vehicle designed to transport infantry into battle while providing direct fire support and protection on the battlefield.
-
D.
reconnaissance aircraft
A reconnaissance aircraft is a specialized military or intelligence-gathering airplane designed to observe, monitor, and collect information about enemy forces, terrain, or strategic targets using advanced sensors and surveillance equipment.
-
E.
8×8 wheeled armoured vehicle
An 8×8 wheeled armoured vehicle is a highly mobile, eight-wheeled military platform designed to transport troops or specialized equipment while providing protection, firepower, and off-road capability.
- 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_69a4937c9c188190aaa216f6b466f452 |
completed | March 1, 2026, 7:29 p.m. |
Created at: March 1, 2026, 7:38 p.m.