Triple
T30349945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fate/Grand Order |
E771965
|
entity |
| Predicate | hasServantClass |
P6299
|
FINISHED |
| Object | Saber |
—
|
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: Saber | Statement: [Fate/Grand Order, hasServantClass, Saber]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasServantClass Context triple: [Fate/Grand Order, hasServantClass, Saber]
-
A.
hasServant
Indicates that one entity has another entity serving it in a subordinate or attendant role.
-
B.
hasServiceClass
chosen
Indicates that an entity is associated with, or categorized under, a particular class or type of service.
-
C.
servantClass
Indicates that one entity serves another in a subordinate or service-oriented role or category.
-
D.
servantClassCommanded
Indicates that one entity, acting as a master or superior, issues commands to another entity in a servant or subordinate role.
-
E.
hasNumberOfServicesClasses
Indicates the relationship that specifies how many service classes are associated with a given 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_69f2248b9a208190bc3e6804acd5afd6 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe9dfaa2d08190b2084f63f842eb6b |
completed | May 9, 2026, 2:37 a.m. |
| PD | Predicate disambiguation | batch_69fe9bba947c81908b0b2b92a4d19b37 |
completed | May 9, 2026, 2:28 a.m. |
Created at: April 29, 2026, 7:56 p.m.