Triple
T30726296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caster (Fate/Zero) |
E782287
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | character in Fate/Zero |
C56768
|
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: character in Fate/Zero Context triple: [Caster (Fate/Zero), instanceOf, character in Fate/Zero]
-
A.
Fate series character
A Fate series character is a heroic or mythical figure summoned as a powerful "Servant" with unique abilities, Noble Phantasms, and a distinct personality shaped by both legend and the narrative’s reinterpretation.
-
B.
Fate/Grand Order character
A Fate/Grand Order character is a summoned heroic spirit or mythic figure, reimagined with unique abilities, personality, and narrative role within the game's overarching story and combat system.
-
C.
Holy Grail War participant
chosen
A Holy Grail War participant is an individual chosen or contracted to compete in a ritual battle royale, commanding or embodying powerful heroic spirits to obtain the omnipotent wish-granting Holy Grail.
-
D.
organization in Fate/Grand Order
An organization in Fate/Grand Order is a structured group of characters—such as Chaldea, mage associations, or villainous factions—united by shared goals, resources, and hierarchies that drive major narrative and gameplay events.
-
E.
Fate/Grand Order story chapter
A Fate/Grand Order story chapter is a structured narrative segment within the game that advances the overarching plot through battles, dialogue, and character development in a specific setting or singularity.
- 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_69f224ad9f9c81908e02a79ae0001137 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:36 p.m.