Triple
T2557980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bitcoin Law in El Salvador |
E56772
|
entity |
| Predicate | priceDisplayRequirement |
P28150
|
FINISHED |
| Object | prices may be expressed in Bitcoin |
—
|
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: prices may be expressed in Bitcoin | Statement: [Bitcoin Law in El Salvador, priceDisplayRequirement, prices may be expressed in Bitcoin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: priceDisplayRequirement Context triple: [Bitcoin Law in El Salvador, priceDisplayRequirement, prices may be expressed in Bitcoin]
-
A.
priceDeterminedBy
Indicates that the price of one entity is set, influenced, or calculated based on another entity or factor.
-
B.
isValuePriced
Indicates that something is offered at a relatively low or favorable price compared to typical or premium alternatives.
-
C.
priceReference
Indicates a relationship where one price is used as a benchmark or basis for determining, comparing, or deriving another price.
-
D.
hasPriceUnit
chosen
Indicates that a price value is expressed in a specific unit of currency or measurement.
-
E.
purchasePrice
Indicates the monetary amount paid or agreed to be paid to acquire something in a purchase transaction.
- 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_69ab4a4bfec081908039988ec4c86e28 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd35c6ee88190b6eaa1841d3e99a4 |
completed | March 7, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69abd0caeb488190b0dd8e48d0f2777d |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:48 p.m.