Triple
T19878671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reichsthaler |
E477706
|
entity |
| Predicate | valueBasedOn |
P120595
|
FINISHED |
| Object | silver content |
—
|
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: silver content | Statement: [Reichsthaler, valueBasedOn, silver content]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: valueBasedOn Context triple: [Reichsthaler, valueBasedOn, silver content]
-
A.
basedOnValues
Indicates that something is determined, derived, or decided according to specified values or value-based criteria.
-
B.
valuedBy
Indicates that one entity is regarded as important, useful, or held in high esteem by another entity.
-
C.
valueDefinedBy
chosen
Indicates that the value of one entity is determined, specified, or constrained by another entity.
-
D.
basedOnBy
Indicates that one entity is derived from, justified by, or constructed using another entity as its source, foundation, or reference.
-
E.
isValuedFor
Indicates that one entity is appreciated, esteemed, or considered important because of a particular quality, contribution, or characteristic it provides to another entity.
- 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_69d8e51f32b08190b3687f4f60353250 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e658dd869c81908aed91ee767f5f3d |
completed | April 20, 2026, 4:48 p.m. |
| PD | Predicate disambiguation | batch_69e537e8c4e481909fe95d795b4864e7 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:52 p.m.