Triple
T37508140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Command Table |
E932148
|
entity |
| Predicate | hasCurrencySink |
P197186
|
FINISHED |
| Object | Anima costs for missions |
—
|
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: Anima costs for missions | Statement: [Command Table, hasCurrencySink, Anima costs for missions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCurrencySink Context triple: [Command Table, hasCurrencySink, Anima costs for missions]
-
A.
hasSettlementCurrency
Indicates that a financial transaction, contract, or account is settled using a specified currency.
-
B.
hasCurrencyProject
Indicates that an entity is associated with or involved in a specific currency-related project.
-
C.
hasMonetaryComponent
Indicates that something includes, involves, or is associated with a monetary or financial element.
-
D.
usesCurrency
Indicates that one entity conducts its financial transactions or values using the monetary unit represented by the other entity.
-
E.
containsCurrencySymbols
Indicates that the subject includes one or more currency symbols within its content or representation.
- 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_69f76ec5268481909ea01c73aeeefd42 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe7b1c506c8190869c1a22031e0571 |
completed | May 9, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69fe796b2bdc8190a86980d44008f875 |
completed | May 9, 2026, 12:01 a.m. |
| PDg | Predicate description generation | batch_69fe7b1b3460819081172731b52ac15b |
completed | May 9, 2026, 12:08 a.m. |
Created at: May 3, 2026, 4:17 p.m.