Triple

T199303
Position Surface form Disambiguated ID Type / Status
Subject Egyptian pound E4066 entity
Predicate hasInflation P8010 FINISHED
Object yes 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: yes | Statement: [Egyptian pound, hasInflation, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasInflation
Context triple: [Egyptian pound, hasInflation, yes]
  • A. inflationRateAfter
    Indicates the rate of inflation that applies following a specified time, event, or reference point.
  • B. inflationRateBefore
    Indicates that one inflation rate occurred earlier in time than another inflation rate being considered.
  • C. isPegged
    Indicates that one entity’s value, status, or behavior is fixed or tightly linked to that of another entity, typically so that changes in the reference entity directly determine changes in the pegged entity.
  • D. isLegalTenderFor
    Indicates that a particular currency or form of money is officially recognized by a governing authority as valid payment for debts and financial transactions within a specified jurisdiction.
  • E. isFloatingCurrency
    Indicates that a currency’s value is determined by market forces and allowed to fluctuate freely rather than being fixed to another asset or currency.
  • F. None of above. chosen

Provenance (4 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_69a254bca59881909a15e1496f1508c7 completed Feb. 28, 2026, 2:36 a.m.
NER Named-entity recognition batch_69a25bcc6dc88190b8c24b485588dfe4 completed Feb. 28, 2026, 3:06 a.m.
PD Predicate disambiguation batch_69a25b4886b48190b46fd2244648a098 completed Feb. 28, 2026, 3:04 a.m.
PDg Predicate description generation batch_69a25bc6ba208190aa8bec59d32f95fd completed Feb. 28, 2026, 3:06 a.m.
Created at: Feb. 28, 2026, 2:44 a.m.