Triple
T529760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peruvian sol |
E10998
|
entity |
| Predicate | belongsToCurrencySystem |
P188
|
FINISHED |
| Object | Peruvian monetary system |
—
|
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: Peruvian monetary system | Statement: [Peruvian sol, belongsToCurrencySystem, Peruvian monetary system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToCurrencySystem Context triple: [Peruvian sol, belongsToCurrencySystem, Peruvian monetary system]
-
A.
definedMonetarySystem
Indicates that an authority or entity has established and specified the rules, structure, and characteristics of a particular monetary system.
-
B.
associatedCurrencyCode
Indicates the currency code that is linked to or used in connection with the given entity or transaction.
-
C.
currencyType
Indicates the specific kind of monetary unit or currency associated with an entity or transaction.
-
D.
usesCurrency
chosen
Indicates that one entity conducts its financial transactions or values using the monetary unit represented by the other entity.
-
E.
hasCurrencyProject
Indicates that an entity is associated with or involved in a specific currency-related project.
- 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_69a2e84b16c4819088d284c47c3a7968 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f1d4984c8190ac372171b16bb5e4 |
completed | Feb. 28, 2026, 1:47 p.m. |
| PD | Predicate disambiguation | batch_69a2f01ac3ec8190a94a05955532c7fa |
completed | Feb. 28, 2026, 1:39 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.