Triple
T30382788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kirei Kotomine |
E772873
|
entity |
| Predicate | roleInFateZero |
P199811
|
FINISHED |
| Object | supporting antagonist |
—
|
LITERAL 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: supporting antagonist | Statement: [Kirei Kotomine, roleInFateZero, supporting antagonist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInFateZero Context triple: [Kirei Kotomine, roleInFateZero, supporting antagonist]
-
A.
roleInShadowlands
Indicates that one entity has a specific function, position, or significance within the context of the Shadowlands.
-
B.
roleInGenpeiWar
Indicates the specific role, position, or involvement an entity had in the events or factions of the Genpei War.
-
C.
roleInTheology
Indicates the specific function, position, or significance an entity holds within a theological system, doctrine, or belief framework.
-
D.
roleInTheProphecy
Indicates that an entity holds a specific function, status, or significance within the context of a particular prophecy.
-
E.
roleInShu
Indicates that an entity holds or plays a specific role within the context of Shu (e.g., the state, domain, or system referred to as Shu).
- F. None of above. chosen
Provenance (4 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_69ff59b33a38819086cc9aa19b81748b |
completed | May 9, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69ff587758f88190a39c2164341dc554 |
completed | May 9, 2026, 3:53 p.m. |
| PDg | Predicate description generation | batch_69ff59b1e2ac8190bb65529e9dbbb178 |
completed | May 9, 2026, 3:58 p.m. |
Created at: April 29, 2026, 8:01 p.m.