Triple
T8657497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Sultan Yacoub |
E205457
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | tank battle |
C647
|
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: tank battle Context triple: [Battle of Sultan Yacoub, instanceOf, tank battle]
-
A.
main battle tank
A main battle tank is a heavily armored, highly mobile, front-line combat vehicle that combines powerful direct-fire weaponry with advanced protection and maneuverability to dominate ground engagements.
-
B.
armored warfare commander
An armored warfare commander is a military leader who plans, coordinates, and directs the tactical employment of armored units—such as tanks and mechanized infantry—to achieve battlefield objectives through mobility, protection, and firepower.
-
C.
battles
chosen
Battles are organized, often large-scale armed conflicts between opposing forces, characterized by strategic maneuvers, tactical engagements, and the pursuit of specific military objectives within a defined time and place.
-
D.
tank armour
Tank armour is the protective material and structural design applied to a tank’s hull and turret to resist and mitigate damage from enemy fire, explosives, and other battlefield threats.
-
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_69ca8350897c819086cde7596fbe5fe7 |
completed | March 30, 2026, 2:06 p.m. |
Created at: March 30, 2026, 6:30 p.m.