Triple
T22871523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Praia de Calhetas |
E567207
|
entity |
| Predicate | moedaLocal |
P78277
|
FINISHED |
| Object | real brasileiro |
—
|
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: real brasileiro | Statement: [Praia de Calhetas, moedaLocal, real brasileiro]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: moedaLocal Context triple: [Praia de Calhetas, moedaLocal, real brasileiro]
-
A.
localCurrency
chosen
Indicates that a particular currency is officially used or recognized as the standard medium of exchange within a specific locality, region, or country.
-
B.
currencyNameLocal
Indicates the name of a currency as expressed in the local or native language of the region where it is used.
-
C.
currencyNameLocalScript
Indicates that a currency’s name is given in the local or native writing system of the region where it is used.
-
D.
monetaryUnitOfAccount
Indicates that something serves as the standard unit in which the value of goods, services, and financial transactions is measured and recorded.
-
E.
currencyCountry
Indicates that a given currency is officially used as legal tender in a particular country.
- 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_69e24589d8348190b96422d13a678bc1 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17f05c688819097ba3d24ea8e52f5 |
completed | April 29, 2026, 3:46 a.m. |
| PD | Predicate disambiguation | batch_69eed2d8c0608190afef4c4e530c0e2c |
completed | April 27, 2026, 3:07 a.m. |
Created at: April 17, 2026, 3:38 p.m.