Triple

T2557981
Position Surface form Disambiguated ID Type / Status
Subject Bitcoin Law in El Salvador E56772 entity
Predicate taxTreatment P23810 FINISHED
Object tax contributions can be paid 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: tax contributions can be paid in Bitcoin | Statement: [Bitcoin Law in El Salvador, taxTreatment, tax contributions can be paid in Bitcoin]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: taxTreatment
Context triple: [Bitcoin Law in El Salvador, taxTreatment, tax contributions can be paid in Bitcoin]
  • A. taxType
    Indicates the specific category or classification of tax that applies to an entity, transaction, or amount.
  • B. taxationMethod chosen
    Indicates the specific way or system by which taxes are calculated, collected, or applied in a given context.
  • C. taxOn
    Indicates that one entity imposes or applies a tax on another entity or item.
  • D. taxRegime
    Indicates the system or structure of taxation that governs how taxes are assessed, collected, and applied within a particular context or jurisdiction.
  • E. taxAuthority
    Indicates that an entity serves as the official body responsible for assessing, collecting, and enforcing taxes over another entity or within a jurisdiction.
  • 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.