Triple
T30345555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unlimited Blade Works route |
E771859
|
entity |
| Predicate | centralServant |
P4079
|
FINISHED |
| Object | Archer |
—
|
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 | Statement: [Unlimited Blade Works route, centralServant, Archer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralServant Context triple: [Unlimited Blade Works route, centralServant, Archer]
-
A.
servantSystem
Indicates a relationship where one system functions in a subordinate or supporting role to another, carrying out tasks or services on its behalf.
-
B.
servantType
Indicates the specific role or category of service that one entity performs in relation to another.
-
C.
hasServant
chosen
Indicates that one entity has another entity serving it in a subordinate or attendant role.
-
D.
treatsServants
Indicates how an entity behaves toward or deals with its servants.
-
E.
servantClass
Indicates that one entity serves another in a subordinate or service-oriented role or category.
- 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_69f7bbf906d8819099020e548dd56bc9 |
completed | May 3, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a2dcf88190a7c9e109e41267be |
completed | May 3, 2026, 9:09 p.m. |
Created at: April 29, 2026, 7:55 p.m.