Triple
T30726004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fate/stay night |
E782280
|
entity |
| Predicate | notableServantClass |
P20971
|
FINISHED |
| Object | Saber |
E771867
|
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: Saber | Statement: [Fate/stay night, notableServantClass, Saber]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableServantClass Context triple: [Fate/stay night, notableServantClass, Saber]
-
A.
notableServant
Indicates that one entity serves another in a particularly distinguished, prominent, or historically significant capacity.
-
B.
servantType
Indicates the specific role or category of service that one entity performs in relation to another.
-
C.
notableCharacterType
chosen
Indicates that an entity is a notable or prominent example of a specified character type or role.
-
D.
notableNoble
Indicates that an entity is a noble who is particularly prominent, distinguished, or widely recognized in some notable way.
-
E.
servantClass
Indicates that one entity serves another in a subordinate or service-oriented role or category.
- F. None of above.
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_69f224ad9f9c81908e02a79ae0001137 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a28b088955881909f995b45a45fc4bc |
completed | June 10, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 8:36 p.m.