Triple
T30345564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unlimited Blade Works route |
E771859
|
entity |
| Predicate | featuresSystem |
P201345
|
FINISHED |
| Object | Holy Grail War |
—
|
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: Holy Grail War | Statement: [Unlimited Blade Works route, featuresSystem, Holy Grail War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresSystem Context triple: [Unlimited Blade Works route, featuresSystem, Holy Grail War]
-
A.
featuresDemon
Indicates that an entity includes, depicts, or prominently involves a demon.
-
B.
featuresSuit
Indicates that one entity includes or presents a particular suit (e.g., clothing, armor, or outfit) as a notable component or attribute.
-
C.
featuresService
Indicates that one entity provides, includes, or offers a particular service as a notable characteristic or component.
-
D.
featuresIn
Indicates that an entity appears or plays a role within another entity, such as a person or element being included in a work, event, or context.
-
E.
featuresMode
Indicates that one entity operates in, supports, or is characterized by a particular mode or configuration specified by another entity.
- F. None of above. chosen
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_69f2248b9a208190bc3e6804acd5afd6 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69ffecdcbac4819093b725a7dbe0e61b |
completed | May 10, 2026, 2:26 a.m. |
| PD | Predicate disambiguation | batch_69ffec3633288190adbbd84e277708dc |
completed | May 10, 2026, 2:23 a.m. |
| PDg | Predicate description generation | batch_69ffecdbe62081909f901e7d4db69d60 |
completed | May 10, 2026, 2:26 a.m. |
Created at: April 29, 2026, 7:55 p.m.