Triple
T30349992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fate/Grand Order |
E771965
|
entity |
| Predicate | hasRaritySystem |
P153679
|
FINISHED |
| Object | 1-star to 5-star Servants |
—
|
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: 1-star to 5-star Servants | Statement: [Fate/Grand Order, hasRaritySystem, 1-star to 5-star Servants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRaritySystem Context triple: [Fate/Grand Order, hasRaritySystem, 1-star to 5-star Servants]
-
A.
rarity
Indicates how uncommon or infrequently an entity or event occurs relative to others in a given context.
-
B.
includesRarities
chosen
Indicates that one entity contains or encompasses specific rare or uncommon items, features, or elements associated with another entity.
-
C.
rarityReason
Indicates the underlying cause or justification for why something is considered rare.
-
D.
inUniverseRarity
Indicates how rare or uncommon something is within the context of a specific fictional or defined universe.
-
E.
instrumentRarity
Indicates how uncommon or scarce an instrument is relative to others.
- 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_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
Created at: April 29, 2026, 7:56 p.m.