Triple
T34895535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tabatinga |
E1006421
|
entity |
| Predicate | usesCurrencyInformally |
P188
|
FINISHED |
| Object | Colombian peso |
—
|
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: Colombian peso | Statement: [Tabatinga, usesCurrencyInformally, Colombian peso]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesCurrencyInformally Context triple: [Tabatinga, usesCurrencyInformally, Colombian peso]
-
A.
usesCurrency
chosen
Indicates that one entity conducts its financial transactions or values using the monetary unit represented by the other entity.
-
B.
usesCurrencyAbbreviation
Indicates that one entity represents or denotes the abbreviated form of the currency used by another entity.
-
C.
usesCurrencyInitially
Indicates that an entity originally adopts or operates with a particular currency at the start of a defined period or process.
-
D.
usesCurrentCurrenciesOf
Indicates that one entity adopts and operates with the same official currencies that are currently in use in another entity.
-
E.
currencyPractice
Indicates the customary or standard way a particular currency is used, represented, or managed in transactions or economic contexts.
- 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_69f76dbfe5788190ad8b64f241f470c8 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fdbc5ef46c8190bbcfb9798f4615b7 |
completed | May 8, 2026, 10:35 a.m. |
| PD | Predicate disambiguation | batch_69fdbb270338819082ce3f73903e884f |
completed | May 8, 2026, 10:29 a.m. |
Created at: May 3, 2026, 4 p.m.