Triple

T30382758
Position Surface form Disambiguated ID Type / Status
Subject Rin Tohsaka E772872 entity
Predicate routeProtagonist P9202 FINISHED
Object Unlimited Blade Works route of Fate/stay night NE NERFINISHED

How this triple was built (2 steps)

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.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Unlimited Blade Works route of Fate/stay night | Statement: [Rin Tohsaka, routeProtagonist, Unlimited Blade Works route of Fate/stay night]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: routeProtagonist
Context triple: [Rin Tohsaka, routeProtagonist, Unlimited Blade Works route of Fate/stay night]
  • A. roleForProtagonist
    Indicates the specific narrative or functional role that an entity plays in relation to the story’s main protagonist.
  • B. mainProtagonist chosen
    Indicates that the subject is the central character or primary focus in the narrative of the related work.
  • C. protagonistAction
    Indicates that the referenced entity performs the central or primary action associated with the main character in a narrative or scenario.
  • D. routeOf
    Indicates that one entity is the path, course, or trajectory taken or followed by another entity (such as a vehicle, shipment, or signal).
  • E. ruleOfProtagonist
    Indicates that the subject holds governing authority or dominion over the protagonist.
  • F. None of above.

Provenance (3 batches)

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_69f2248e3444819081b05712dc6873de completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f6851aeb948190b674200cf6bf51f9 completed May 2, 2026, 11:13 p.m.
PD Predicate disambiguation batch_69f678d019fc8190913662cd2f87b857 completed May 2, 2026, 10:21 p.m.
Created at: April 29, 2026, 8:01 p.m.