Triple
T9175735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fate/Grand Order - First Order |
E220194
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | anime television special |
C24493
|
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: anime television special Context triple: [Fate/Grand Order - First Order, instanceOf, anime television special]
-
A.
animated television special
chosen
An animated television special is a standalone, longer-than-standard TV program that uses animation to tell a self-contained story, often produced for a specific event, holiday, or promotional occasion.
-
B.
adult animated television special
An adult animated television special is a standalone, feature-length or extended animated program created primarily for mature audiences, often featuring complex themes, explicit content, or sophisticated humor not intended for children.
-
C.
American television special
An American television special is a standalone, typically one-time or limited-run broadcast program produced for U.S. television that falls outside the regular episodic series format, often created for holidays, events, or unique occasions.
-
D.
animated television character
An animated television character is a fictional persona brought to life through drawn or computer-generated imagery, designed to act, speak, and evolve within the narrative of a TV series.
-
E.
anime character
An anime character is a stylized, often exaggerated fictional persona originating from Japanese animation, defined by distinctive visual design, expressive emotions, and participation in narrative-driven stories.
- 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_69ca83e589948190ac9907819db11ddf |
completed | March 30, 2026, 2:08 p.m. |
Created at: March 30, 2026, 7:23 p.m.