Triple
T27023529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tachileik |
E680726
|
entity |
| Predicate | usesForeignCurrencyInformally |
P10274
|
FINISHED |
| Object | Thai baht |
—
|
NE NERFINISHED |
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: Thai baht | Statement: [Tachileik, usesForeignCurrencyInformally, Thai baht]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesForeignCurrencyInformally Context triple: [Tachileik, usesForeignCurrencyInformally, Thai baht]
-
A.
usesCurrency
Indicates that one entity conducts its financial transactions or values using the monetary unit represented by the other entity.
-
B.
usesCurrencyInitially
Indicates that an entity originally adopts or operates with a particular currency at the start of a defined period or process.
-
C.
usesSupplementaryCurrency
chosen
Indicates that an entity employs an additional, non-primary currency alongside its main currency for transactions or value exchange.
-
D.
usesExchangeRateRegime
Indicates that one entity adopts or operates under a particular exchange rate regime in conducting its currency or monetary arrangements.
-
E.
currencyNotUnified
Indicates that the entities involved do not share a single common currency or monetary system.
- 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_69eeeb5450988190bfc9a3c012ac463a |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f6222ec35c819086b41052677212e1 |
completed | May 2, 2026, 4:11 p.m. |
| PD | Predicate disambiguation | batch_69f620e0b37481909a280574decbd443 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 7:09 a.m.