Triple
T18291840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Larsen Islands |
E438134
|
entity |
| Predicate | hasOfficialCurrency |
P36099
|
FINISHED |
| Object | none |
—
|
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: none | Statement: [Larsen Islands, hasOfficialCurrency, none]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOfficialCurrency Context triple: [Larsen Islands, hasOfficialCurrency, none]
-
A.
representsOfficialCurrency
chosen
Indicates that one entity serves as the official legal tender or primary currency used within the jurisdiction or authority of another entity.
-
B.
officialNameOfCurrency
Indicates the officially designated name of a particular currency used by an entity.
-
C.
currencyOfOfficialEmblem
Indicates the currency that is depicted or symbolically represented on an official emblem.
-
D.
isWorldTradeCurrency
Indicates that a currency is officially used and widely accepted as a medium of exchange in international trade and global financial transactions.
-
E.
hasDominantCurrency
Indicates that one currency is the primary or controlling medium of exchange or valuation within a given context, such as a market, region, or financial 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_69d8b914530c8190b4474d862a2b2a1b |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e501000bd881909ae64ab64219bef6 |
completed | April 19, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69e44fdf43d08190bbcfb6b1fe3cc0ee |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:35 a.m.