Triple
T18152708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Asakai |
E434547
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | EVE Online 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: EVE Online battle Context triple: [Battle of Asakai, instanceOf, EVE Online battle]
-
A.
EVE Online game server
The EVE Online game server is a large-scale, distributed backend system that simulates a persistent single-shard universe, handling player interactions, economy, combat, and world state in real time for all connected clients.
-
B.
carrier battle
A carrier battle is a large-scale naval engagement centered around aircraft carriers projecting air power, where opposing fleets use carrier-based aircraft, escorts, and support vessels to attack and defend over vast maritime distances.
-
C.
battle course
A battle course is a structured training environment or program designed to simulate combat scenarios and develop participants’ tactical, physical, and strategic skills.
-
D.
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.
-
E.
battlecruiser class
A battlecruiser class represents a large, fast, heavily armed warship optimized for long-range offensive power at the expense of some armor protection compared to battleships.
- 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_69d8b90aac308190801e2c57d8c5bfe5 |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:29 a.m.