Triple
T30349989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fate/Grand Order |
E771965
|
entity |
| Predicate | usesInGameCurrency |
P188
|
FINISHED |
| Object | Saint Quartz |
—
|
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: Saint Quartz | Statement: [Fate/Grand Order, usesInGameCurrency, Saint Quartz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesInGameCurrency Context triple: [Fate/Grand Order, usesInGameCurrency, Saint Quartz]
-
A.
inGameCurrency
Indicates that one entity functions as a form of currency or medium of exchange within the context of a specific game.
-
B.
currencyUsedInCasino
Indicates that a particular type of currency is accepted and used for gambling transactions within a casino.
-
C.
canBePurchasedWith
Indicates that one entity is able to be bought or acquired using another entity as the form of payment.
-
D.
usesCurrency
chosen
Indicates that one entity conducts its financial transactions or values using the monetary unit represented by the other entity.
-
E.
currencyUsedFor
Indicates that a particular currency is used as the medium of exchange or legal tender for a given entity, such as a country, region, or organization.
- 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_69f68a16debc8190a12f5f65ced055d7 |
completed | May 2, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f6860def1c81909d79e1f088c4b5e5 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 7:56 p.m.