Triple
T31439529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rogueport Inn |
E802028
|
entity |
| Predicate | hasInUniverseCurrency |
P92315
|
FINISHED |
| Object | coins |
—
|
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: coins | Statement: [Rogueport Inn, hasInUniverseCurrency, coins]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInUniverseCurrency Context triple: [Rogueport Inn, hasInUniverseCurrency, coins]
-
A.
inUniverseCurrencyUse
chosen
Indicates that a currency is used as legal tender or medium of exchange within a particular fictional or defined universe.
-
B.
currencyOnboard
Indicates that a particular currency has been enabled, registered, or made available for use within a given system or context.
-
C.
currencyOrTradeTool
Indicates that something functions as a medium of exchange, either as a currency or as a tool directly used in trade or barter.
-
D.
usesCurrency
Indicates that one entity conducts its financial transactions or values using the monetary unit represented by the other entity.
-
E.
isBasketCurrency
Indicates that a currency functions as a composite or basket currency made up of multiple underlying currencies or assets.
- 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_69f348c5a6bc819092a557e95438976f |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69ff3b32ee148190a3ba3b7600943fef |
completed | May 9, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_69ff3a238af88190a2c2245e30299e48 |
completed | May 9, 2026, 1:44 p.m. |
Created at: April 30, 2026, 9:04 p.m.