Triple
T30382736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rin Tohsaka |
E772872
|
entity |
| Predicate | commandSevant |
P2333
|
FINISHED |
| Object | Archer (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: Archer (Fate/stay night) | Statement: [Rin Tohsaka, commandSevant, Archer (Fate/stay night)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commandSevant Context triple: [Rin Tohsaka, commandSevant, Archer (Fate/stay night)]
-
A.
commands
chosen
Indicates that one entity holds authority over another and issues directives or orders that the other is expected to follow.
-
B.
commandOf
Indicates that one entity holds authoritative control or leadership over another, typically in a military, organizational, or hierarchical context.
-
C.
commandType
Indicates the specific kind or category of command being issued or executed in the relationship.
-
D.
commandSet
Indicates that one entity issues or defines a specific set of commands for another entity or system to follow.
-
E.
commandsIn
Indicates that one entity contains, defines, or includes the set of commands that are available or applicable within another entity.
- 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_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
Created at: April 29, 2026, 8:01 p.m.