Triple

T11905599
Position Surface form Disambiguated ID Type / Status
Subject Linked Exchange Rate System E283264 entity
Predicate lowerExchangeRateBound P17139 FINISHED
Object 7.75 HKD per 1 USD 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: 7.75 HKD per 1 USD | Statement: [Linked Exchange Rate System, lowerExchangeRateBound, 7.75 HKD per 1 USD]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: lowerExchangeRateBound
Context triple: [Linked Exchange Rate System, lowerExchangeRateBound, 7.75 HKD per 1 USD]
  • A. lowerLimit chosen
    Indicates that one value serves as the minimum or smallest allowable bound or threshold for another value or range.
  • B. lowerBandWidth
    Indicates that one entity has a smaller or more limited bandwidth capacity than another.
  • C. lowEnergyLimit
    Indicates a relationship where an entity is constrained by or subject to a minimum allowable energy level or threshold.
  • D. lowerDenomination
    Indicates that one entity represents a monetary unit of smaller value than another entity within the same currency system.
  • E. lowerValueIndicates
    Indicates that a smaller numerical value of a property or measurement corresponds to a greater degree, better outcome, or stronger presence of the relevant characteristic.
  • 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_69d6ab2c07e88190ba13b0d21fd6cf33 completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d8e525460c81909d855048d9c799bf completed April 10, 2026, 11:55 a.m.
PD Predicate disambiguation batch_69d8bb2fca4481909893f3428b0871ac completed April 10, 2026, 8:56 a.m.
Created at: April 8, 2026, 9:44 p.m.