Triple
T30483581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phantasy Star Online Episode III: C.A.R.D. Revolution |
E775653
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | online role-playing game |
C4648
|
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: online role-playing game Context triple: [Phantasy Star Online Episode III: C.A.R.D. Revolution, instanceOf, online role-playing game]
-
A.
role‑playing game
chosen
A role-playing game is an interactive experience in which players assume fictional characters and collaboratively create or influence a narrative by making choices that affect the game world and its outcomes.
-
B.
action role-playing game series
An action role-playing game series is a collection of related video games that blend real-time combat and character control with role-playing elements such as character progression, narrative choices, and equipment customization across multiple interconnected titles.
-
C.
MUD
A MUD (Multi-User Dungeon) is a text-based, multi-user virtual world where players interact, explore, and role-play in a shared environment, often featuring RPG-style mechanics.
-
D.
role-playing game engine
A role-playing game engine is a software framework that provides the core systems—such as character progression, combat mechanics, dialogue, inventory, and world interaction—needed to build and run role-playing games.
-
E.
online gaming company
An online gaming company is a business that develops, publishes, and/or operates digital games delivered over the internet, providing interactive entertainment and related services to players worldwide.
- 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_69f22497f91c8190afa7165bc900accd |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:13 p.m.