Triple

T30383573
Position Surface form Disambiguated ID Type / Status
Subject Fate series E772890 entity
Predicate notableWork P4 FINISHED
Object Fate/Prototype
Fate/Prototype is an anime OVA and conceptual predecessor to Fate/stay night, showcasing an earlier version of the Holy Grail War story and its characters within the Fate franchise.
E1942629 NE FINISHED

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: Fate/Prototype | Statement: [Fate series, notableWork, Fate/Prototype]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Fate/Prototype
Triple: [Fate series, notableWork, Fate/Prototype]
Generated description
Fate/Prototype is an anime OVA and conceptual predecessor to Fate/stay night, showcasing an earlier version of the Holy Grail War story and its characters within the Fate franchise.

Provenance (5 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_69f6851c44108190822e8d70e1114e09 completed May 2, 2026, 11:13 p.m.
NED1 Entity disambiguation (via context triple) batch_6a29180bc3d481908b8596b6c44b8e54 completed June 10, 2026, 7:53 a.m.
NEDg Description generation batch_6a29198f92548190ae85189da09f9bcf completed June 10, 2026, 8 a.m.
NED2 Entity disambiguation (via description) batch_6a291b07a2708190ad269cae52e1dba5 completed June 10, 2026, 8:06 a.m.
Created at: April 29, 2026, 8:01 p.m.