Triple
T2099120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dutch rijksdaalder |
E37051
|
entity |
| Predicate | relativeValue |
P9543
|
FINISHED |
| Object | high-value coin in everyday transactions |
—
|
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: high-value coin in everyday transactions | Statement: [Dutch rijksdaalder, relativeValue, high-value coin in everyday transactions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeValue Context triple: [Dutch rijksdaalder, relativeValue, high-value coin in everyday transactions]
-
A.
relativePrice
chosen
Indicates a comparison of the cost or monetary value of one entity relative to another.
-
B.
relativeLevel
Indicates a comparative relationship specifying how one entity’s level, degree, or intensity of some property stands relative to that of another entity.
-
C.
valuedBy
Indicates that one entity is regarded as important, useful, or held in high esteem by another entity.
-
D.
relativePosition
Indicates the spatial relationship of one entity’s location with respect to another entity’s position.
-
E.
value
Indicates that one entity possesses, represents, or corresponds to a particular quantity, quality, or assigned worth.
- 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_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. |
Created at: March 4, 2026, 7:43 p.m.