Triple
T29617273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Artanis |
E754895
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | StarCraft character |
C4830
|
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: StarCraft character Context triple: [Artanis, instanceOf, StarCraft character]
-
A.
StarCraft faction
A StarCraft faction is a distinct playable race or group, defined by unique units, technologies, and strategic mechanics that shape a player’s playstyle and tactics in the StarCraft universe.
-
B.
Starship Troopers character
A Starship Troopers character is an individual—human or alien—who exists within the militaristic, satirical sci-fi universe of Starship Troopers, defined by their role in interstellar warfare, political ideology, and interactions with the series’ themes of duty, citizenship, and propaganda.
-
C.
StarCraft II player
A StarCraft II player is an individual who strategically controls units and resources in real time to outmaneuver and defeat opponents within the game's competitive sci-fi environment.
-
D.
character from Warcraft franchise
A character from the Warcraft franchise is a fictional individual—such as a hero, villain, or supporting figure—who exists within the Warcraft universe’s lore, games, and media, possessing distinct abilities, backstory, and affiliations with its various races and factions.
-
E.
video game character
chosen
A video game character is a fictional, interactive entity within a game world that the player controls or encounters, defined by its abilities, appearance, behavior, and role in the game's narrative or mechanics.
- 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_69f0ef85f62081909842b59fdf8717e1 |
completed | April 28, 2026, 5:33 p.m. |
Created at: April 28, 2026, 6:32 p.m.