Triple
T30261063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metal Slug Attack |
E769491
|
entity |
| Predicate | hasCurrencyType |
P11731
|
FINISHED |
| Object | medals |
—
|
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: medals | Statement: [Metal Slug Attack, hasCurrencyType, medals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCurrencyType Context triple: [Metal Slug Attack, hasCurrencyType, medals]
-
A.
currencyType
chosen
Indicates the specific kind of monetary unit or currency associated with an entity or transaction.
-
B.
isPhysicalCurrency
Indicates that something functions as tangible money in the form of physical coins or banknotes, rather than digital or electronic currency.
-
C.
hasSettlementCurrency
Indicates that a financial transaction, contract, or account is settled using a specified currency.
-
D.
usesCurrency
Indicates that one entity conducts its financial transactions or values using the monetary unit represented by the other entity.
-
E.
hasDominantCurrency
Indicates that one currency is the primary or controlling medium of exchange or valuation within a given context, such as a market, region, or financial system.
- 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_69f22484a5f48190b678cd607700bc82 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fce7671f108190bf3ebf54339068b5 |
completed | May 7, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69fce5b5a84c81908ac1b5b9f08d48d0 |
completed | May 7, 2026, 7:19 p.m. |
Created at: April 29, 2026, 7:42 p.m.