Triple

T4605757
Position Surface form Disambiguated ID Type / Status
Subject Zambian kwacha E100429 entity
Predicate reasonForRebasing P5019 FINISHED
Object remove three zeros from denominations 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: remove three zeros from denominations | Statement: [Zambian kwacha, reasonForRebasing, remove three zeros from denominations]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: reasonForRebasing
Context triple: [Zambian kwacha, reasonForRebasing, remove three zeros from denominations]
  • A. reasonForMerger
    Indicates the underlying cause, motivation, or justification for why two or more entities merged.
  • B. reasonForChange
    Indicates that one entity serves as the cause, justification, or motivation for a modification or change in another entity or state.
  • C. reasonForConflict
    Indicates that one entity is the cause, motive, or underlying issue leading to a conflict involving another entity.
  • D. changeReason chosen
    Indicates the reason or justification for a modification or change made to an entity or its state.
  • E. reasonForReintegration
    Indicates the circumstance, cause, or justification that led to an entity being brought back or restored to a previous group, system, or status.
  • 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_69bd43cce1e08190a07d53af6a9b6c24 completed March 20, 2026, 12:55 p.m.
NER Named-entity recognition batch_69bd599b1f0881909fd693b81ff44f98 completed March 20, 2026, 2:28 p.m.
PD Predicate disambiguation batch_69bd522e2d5c8190937d0b5574f78f99 completed March 20, 2026, 1:57 p.m.
Created at: March 20, 2026, 1:12 p.m.