Triple
T30345565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unlimited Blade Works route |
E771859
|
entity |
| Predicate | featuresServantClass |
P100346
|
FINISHED |
| Object | Archer class |
—
|
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: Archer class | Statement: [Unlimited Blade Works route, featuresServantClass, Archer class]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresServantClass Context triple: [Unlimited Blade Works route, featuresServantClass, Archer class]
-
A.
servantClassSkill
Indicates a classification or type of skill possessed or used by a servant in relation to their role or function.
-
B.
servantClass
Indicates that one entity serves another in a subordinate or service-oriented role or category.
-
C.
servantType
Indicates the specific role or category of service that one entity performs in relation to another.
-
D.
heroClass
chosen
Indicates the character class or role that a hero belongs to within a given system or context.
-
E.
featuresCharacterWith
Indicates that one entity (such as a work or product) includes or presents a particular character as part of its content.
- 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_69ffed8912488190baa05f572e5b1b89 |
completed | May 10, 2026, 2:29 a.m. |
| PD | Predicate disambiguation | batch_69ffed12a76c8190ad85c6ac869c72e9 |
completed | May 10, 2026, 2:27 a.m. |
Created at: April 29, 2026, 7:55 p.m.