Triple
T473243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hong Kong dollar |
E9004
|
entity |
| Predicate | typicalPegRange |
P13427
|
FINISHED |
| Object | HK$7.75–7.85 per US$1 |
—
|
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: HK$7.75–7.85 per US$1 | Statement: [Hong Kong dollar, typicalPegRange, HK$7.75–7.85 per US$1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPegRange Context triple: [Hong Kong dollar, typicalPegRange, HK$7.75–7.85 per US$1]
-
A.
typicalEnergyRange
Indicates the usual or characteristic range of energy values associated with an entity, process, or interaction.
-
B.
typicalCapacity
Indicates the usual or standard amount, volume, or capability that something is designed or expected to hold, handle, or perform under normal conditions.
-
C.
typicalPenAngle
Indicates the usual or characteristic angle at which a pen is held or positioned during use.
-
D.
typicalHeight
Indicates the usual or characteristic height associated with an entity, such as a person, object, or species.
-
E.
typicalGroupSizeRange
Indicates the usual minimum and maximum number of individuals that typically occur together in a group for the given entity.
- 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_69a2e7ff81708190b0507a24a997232c |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2f0208c788190a96cdabcf593fda7 |
completed | Feb. 28, 2026, 1:39 p.m. |
| PD | Predicate disambiguation | batch_69a2edecefb081908331ef8b9edf6636 |
completed | Feb. 28, 2026, 1:30 p.m. |
| PDg | Predicate description generation | batch_69a2eeba8a488190986cc7381332f783 |
completed | Feb. 28, 2026, 1:33 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.