Triple

T26024613
Position Surface form Disambiguated ID Type / Status
Subject Libyan Armed Forces E647254 entity
Predicate usesCurrencyForBudget P188 FINISHED
Object Libyan dinar NE NERFINISHED

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: Libyan dinar | Statement: [Libyan Armed Forces, usesCurrencyForBudget, Libyan dinar]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesCurrencyForBudget
Context triple: [Libyan Armed Forces, usesCurrencyForBudget, Libyan dinar]
  • A. usesCurrency chosen
    Indicates that one entity conducts its financial transactions or values using the monetary unit represented by the other entity.
  • B. usesCurrencyInitially
    Indicates that an entity originally adopts or operates with a particular currency at the start of a defined period or process.
  • C. inUniverseCurrencyUse
    Indicates that a currency is used as legal tender or medium of exchange within a particular fictional or defined universe.
  • D. currencyUsedFor
    Indicates that a particular currency is used as the medium of exchange or legal tender for a given entity, such as a country, region, or organization.
  • 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_69e77e8b60e88190a3b26c4f0032a2c2 completed April 21, 2026, 1:41 p.m.
NER Named-entity recognition batch_69f65aa07c048190a5df30d53d8f0cf5 completed May 2, 2026, 8:12 p.m.
PD Predicate disambiguation batch_69f659cc571c819097e51e531961d812 completed May 2, 2026, 8:08 p.m.
Created at: April 22, 2026, 9:05 a.m.