Triple
T4465342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tuvaluan dollar |
E98363
|
entity |
| Predicate | banknotesUsed |
P12439
|
FINISHED |
| Object | Australian dollar banknotes |
—
|
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: Australian dollar banknotes | Statement: [Tuvaluan dollar, banknotesUsed, Australian dollar banknotes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: banknotesUsed Context triple: [Tuvaluan dollar, banknotesUsed, Australian dollar banknotes]
-
A.
banknotesIssuedIn
Indicates the relationship where a specific set of banknotes was officially issued or put into circulation within a particular country, region, or jurisdiction.
-
B.
frequentlyUsedBanknotes
chosen
Indicates that the referenced banknotes are commonly or regularly used in transactions within a given context or system.
-
C.
hasBanknotes
Indicates that an entity possesses or contains one or more banknotes.
-
D.
banknoteDenomination
Indicates the specific face value assigned to a banknote in a given currency.
-
E.
issuesBanknotes
Indicates that an entity (typically a central bank or monetary authority) produces and puts banknotes into official circulation as legal tender.
- 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_69b3454a7c608190944f5455c8031d73 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35697937c8190b91f72d9e4f945f6 |
completed | March 13, 2026, 12:13 a.m. |
| PD | Predicate disambiguation | batch_69b34f65f6448190abfadb2ae5658798 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:34 p.m.