Triple
T497628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coinage Act of 1849 |
E10328
|
entity |
| Predicate | appliesToCurrencyType |
P11731
|
FINISHED |
| Object | specie |
—
|
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: specie | Statement: [Coinage Act of 1849, appliesToCurrencyType, specie]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToCurrencyType Context triple: [Coinage Act of 1849, appliesToCurrencyType, specie]
-
A.
usesCurrency
Indicates that one entity conducts its financial transactions or values using the monetary unit represented by the other entity.
-
B.
currencyType
chosen
Indicates the specific kind of monetary unit or currency associated with an entity or transaction.
-
C.
involvesCurrency
Indicates that the relationship or action includes or pertains to the use, exchange, or specification of a particular currency.
-
D.
associatedCurrencyCode
Indicates the currency code that is linked to or used in connection with the given entity or transaction.
-
E.
usesSupplementaryCurrency
Indicates that an entity employs an additional, non-primary currency alongside its main currency for transactions or value exchange.
- 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_69a2e847df8481909239ec08ccf1e376 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f1183e988190bce70932a9678134 |
completed | Feb. 28, 2026, 1:43 p.m. |
| PD | Predicate disambiguation | batch_69a2edfa87cc8190a77c726a5a55b7d9 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.