Triple
T16095211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kreuzer |
E390463
|
entity |
| Predicate | valueRelativeToGulden |
P35954
|
FINISHED |
| Object | 60 kreuzer = 1 gulden (South German standard) |
—
|
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: 60 kreuzer = 1 gulden (South German standard) | Statement: [Kreuzer, valueRelativeToGulden, 60 kreuzer = 1 gulden (South German standard)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: valueRelativeToGulden Context triple: [Kreuzer, valueRelativeToGulden, 60 kreuzer = 1 gulden (South German standard)]
-
A.
valueRelativeToGuilder
chosen
Indicates that something’s value is expressed in terms of, or compared relative to, the guilder currency.
-
B.
valueRelativeToAkçe
Indicates the value of something expressed in terms of, or relative to, the akçe monetary unit.
-
C.
valueInUSD
Indicates that a given amount or asset is expressed or evaluated in terms of its monetary value in United States dollars (USD).
-
D.
valueInPula
Indicates that one entity represents the monetary value of another entity expressed in Botswana pula.
-
E.
ratioToGold
Indicates the proportional relationship between a given quantity and a corresponding amount of gold.
- 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_69d87f198bc48190a8b7e53ca15b7ead |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e1ff63edb0819092cbb671967bbdcd |
completed | April 17, 2026, 9:37 a.m. |
| PD | Predicate disambiguation | batch_69e182804208819087f35307cd6e4103 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:59 a.m.