Triple
T11905601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Linked Exchange Rate System |
E283264
|
entity |
| Predicate | tradingBandWidth |
P94020
|
FINISHED |
| Object | 0.10 HKD per 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: 0.10 HKD per USD | Statement: [Linked Exchange Rate System, tradingBandWidth, 0.10 HKD per USD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tradingBandWidth Context triple: [Linked Exchange Rate System, tradingBandWidth, 0.10 HKD per USD]
-
A.
fluctuationBandWidth
chosen
Indicates the range or width within which a value is allowed or observed to fluctuate over time or conditions.
-
B.
upperBandWidth
Indicates the maximum bandwidth limit or upper threshold of data transfer capacity allowed or supported in a given context.
-
C.
tradingSegment
Indicates that one entity operates within, or is associated with, a specific trading segment or market subdivision for transactional activities.
-
D.
transmissionBand
Indicates the specific frequency range or band over which a signal, wave, or transmission is carried or allowed to pass.
-
E.
tradingApproach
Indicates the method or strategy an entity uses to conduct trading activities or make trade-related decisions.
- 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.