Triple
T9175701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fate/Zero |
E220193
|
entity |
| Predicate | animeCharacterDesigner |
P57050
|
FINISHED |
| Object | Tomonori Sudo |
—
|
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: Tomonori Sudo | Statement: [Fate/Zero, animeCharacterDesigner, Tomonori Sudo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: animeCharacterDesigner Context triple: [Fate/Zero, animeCharacterDesigner, Tomonori Sudo]
-
A.
characterDesigner
chosen
Indicates a relationship where an entity is responsible for designing or creating the visual or conceptual characteristics of a character.
-
B.
characterGenerator
Indicates a relationship where an entity produces, defines, or initializes characters or character data for use in another context.
-
C.
creatorOfCharacter
Indicates that one entity is the originator or author who created or conceived the other entity as a character.
-
D.
fictionalCharacterFrom
Indicates that a fictional character originates from, or is created within, a particular work, universe, or source.
-
E.
petCharacter
Indicates that one entity is a pet belonging to, cared for by, or closely associated with another entity as its owner or companion.
- 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_69ca83e589948190ac9907819db11ddf |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccbfa496548190a096969eebf732f3 |
completed | April 1, 2026, 6:48 a.m. |
| PD | Predicate disambiguation | batch_69cc660761d88190ab6134b43b376964 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:23 p.m.