Triple
T2099116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dutch rijksdaalder |
E37051
|
entity |
| Predicate | wasLegalTender |
P35956
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Dutch rijksdaalder, wasLegalTender, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasLegalTender Context triple: [Dutch rijksdaalder, wasLegalTender, yes]
-
A.
wasLegalTenderAlongside
Indicates that one form of money was officially recognized and accepted as legal tender at the same time as another form of money within a given jurisdiction or period.
-
B.
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.
-
C.
isLegalTenderSince
Indicates that something has held the status of legal tender starting from a specified point in time.
-
D.
legalTenderSince
Indicates the point in time from which something has officially held the status of legal tender within a given jurisdiction.
-
E.
notLegalTenderIn
Indicates that a form of money is not officially recognized as acceptable payment within a specified jurisdiction or region.
- F. None of above. chosen
Provenance (4 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_69a8861828948190924aa30c08806b3a |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abbab9f5b88190b8a18056dc592dde |
completed | March 7, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69abb7b6274081909df36cd7a7c6a675 |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abba2e65b48190bb19cfc4b0f8c462 |
completed | March 7, 2026, 5:39 a.m. |
Created at: March 4, 2026, 7:43 p.m.