Triple
T11283452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loëx |
E267122
|
entity |
| Predicate | usesCurrencyCode |
P188
|
FINISHED |
| Object | CHF |
E27703
|
NE 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: CHF | Statement: [Loëx, usesCurrencyCode, CHF]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: CHF Context triple: [Loëx, usesCurrencyCode, CHF]
-
A.
CHF
chosen
CHF is the official currency code for the Swiss franc, the national currency of Switzerland and Liechtenstein.
-
B.
CHF
CHF (Charging Function) is a 3GPP-defined network function in 5G core architecture responsible for handling online and offline charging, rating, and accounting for network services.
-
C.
CHD
CHD is the IATA airport code for Chandler Municipal Airport, a public general aviation facility serving Chandler, Arizona.
-
D.
HCM
HCM is the commonly used abbreviation for the High Court of Manipur, the highest judicial authority in the Indian state of Manipur.
-
E.
DCM
DCM is the post-nominal abbreviation used to denote recipients of the Distinguished Conduct Medal, a high-level British military decoration for gallantry in the field.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d6aac8c2f48190ad0596f1f89f0470 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9855e8881909bd301718cbd8ca1 |
completed | April 9, 2026, 6:01 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e4f471490081909036362c58e1e727 |
completed | April 19, 2026, 3:27 p.m. |
Created at: April 8, 2026, 9:31 p.m.