Triple

T29603264
Position Surface form Disambiguated ID Type / Status
Subject Provisional Government of Oregon E754507 entity
Predicate alsoUsedCurrency P10274 FINISHED
Object beaver skins 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: beaver skins | Statement: [Provisional Government of Oregon, alsoUsedCurrency, beaver skins]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: alsoUsedCurrency
Context triple: [Provisional Government of Oregon, alsoUsedCurrency, beaver skins]
  • A. usesCurrency
    Indicates that one entity conducts its financial transactions or values using the monetary unit represented by the other entity.
  • B. usesSupplementaryCurrency chosen
    Indicates that an entity employs an additional, non-primary currency alongside its main currency for transactions or value exchange.
  • C. associatedCurrencyCode
    Indicates the currency code that is linked to or used in connection with the given entity or transaction.
  • D. usesCurrencyInitially
    Indicates that an entity originally adopts or operates with a particular currency at the start of a defined period or process.
  • E. involvesCurrency
    Indicates that the relationship or action includes or pertains to the use, exchange, or specification of a particular currency.
  • 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_69f0ef84e5d08190a0df17f5930ceed3 completed April 28, 2026, 5:33 p.m.
NER Named-entity recognition batch_69f66de515a88190aa297e74cb541501 completed May 2, 2026, 9:34 p.m.
PD Predicate disambiguation batch_69f6659d36208190b01412600a4ed57d completed May 2, 2026, 8:59 p.m.
Created at: April 28, 2026, 6:23 p.m.