Triple
T13332037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Mint (historical) |
E317596
|
entity |
| Predicate | associatedWithCurrencyHistory |
P10987
|
FINISHED |
| Object | history of the thaler |
—
|
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: history of the thaler | Statement: [Royal Mint (historical), associatedWithCurrencyHistory, history of the thaler]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithCurrencyHistory Context triple: [Royal Mint (historical), associatedWithCurrencyHistory, history of the thaler]
-
A.
associatedWithHistoricalState
Indicates that an entity has a relationship or connection to a specific historical state or former political entity.
-
B.
hasDenominationHistory
chosen
Indicates that an entity has an associated record or sequence of changes in its denomination over time.
-
C.
coexistedWithCurrency
Indicates that one currency was in circulation at the same time as another currency.
-
D.
hasAssociatedCurrencyEntity
Indicates that an entity is linked to a specific currency entity that represents the monetary unit relevant to it.
-
E.
associatedCurrencyCode
Indicates the currency code that is linked to or used in connection with the given entity or transaction.
- 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_69d806b4d62c81908d4ced1665414be5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d9992fffa0819086610ae3bed2e2f9 |
completed | April 11, 2026, 12:43 a.m. |
| PD | Predicate disambiguation | batch_69d98f6e53d88190bd6aa42f69b10ffb |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:30 p.m.