Triple
T4461195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | litas |
E98257
|
entity |
| Predicate | legalTenderEndDate |
P7629
|
FINISHED |
| Object | 2015-01-15 |
—
|
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: 2015-01-15 | Statement: [litas, legalTenderEndDate, 2015-01-15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalTenderEndDate Context triple: [litas, legalTenderEndDate, 2015-01-15]
-
A.
legalTenderUntil
chosen
Indicates that a form of money is officially recognized as valid payment only up to a specified date or time.
-
B.
legalTenderSince
Indicates the point in time from which something has officially held the status of legal tender within a given jurisdiction.
-
C.
isLegalTenderSince
Indicates that something has held the status of legal tender starting from a specified point in time.
-
D.
wasLegalTender
Indicates that something was officially recognized as valid money for settling debts or transactions within a particular jurisdiction and time period.
-
E.
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.
- 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_69b35674f718819089388c3924dd1414 |
completed | March 13, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69b34f65f6448190abfadb2ae5658798 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:34 p.m.