Triple
T11660901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fast & Furious Crossroads |
E277115
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | vehicular combat game |
C24299
|
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: vehicular combat game Context triple: [Fast & Furious Crossroads, instanceOf, vehicular combat game]
-
A.
combat racing video game
chosen
A combat racing video game is a type of racing game where players drive vehicles while using weapons, power-ups, or physical attacks to hinder opponents and gain an advantage in the race.
-
B.
tactical vehicle
A tactical vehicle is a specialized, often armored, ground transport designed to support military or law-enforcement operations by providing mobility, protection, and mission-specific capabilities in challenging environments.
-
C.
racing video game
A racing video game is an interactive digital game where players control vehicles to compete in speed-based contests on various tracks or environments, often featuring time trials, head-to-head races, and customizable performance or visual options.
-
D.
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.
-
E.
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.
- 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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
Created at: April 8, 2026, 9:39 p.m.