Triple
T37665833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sand Kingdom |
E937817
|
entity |
| Predicate | regionalCoin |
P18115
|
FINISHED |
| Object | Tostarena coin |
—
|
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: Tostarena coin | Statement: [Sand Kingdom, regionalCoin, Tostarena coin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionalCoin Context triple: [Sand Kingdom, regionalCoin, Tostarena coin]
-
A.
sharesCurrencyRegion
Indicates that two entities are located in or associated with geographic areas that use the same official currency.
-
B.
currencyArea
chosen
Indicates that one entity is the geographic or economic region in which the other entity’s currency is officially used or valid.
-
C.
isLegalTenderFor
Indicates that a particular currency or form of money is officially recognized by a governing authority as valid payment for debts and financial transactions within a specified jurisdiction.
-
D.
coinedDenomination
Indicates that an entity created or introduced a particular name, term, or denomination for something.
-
E.
currencyInitiative
Indicates an initiative, program, or action specifically related to the development, regulation, promotion, or reform of a 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a00708ab11081909641d245c4282aa0 |
completed | May 10, 2026, 11:48 a.m. |
| PD | Predicate disambiguation | batch_6a00703daa0081908903ce3a28084d35 |
completed | May 10, 2026, 11:47 a.m. |
Created at: May 3, 2026, 4:18 p.m.