Triple
T25028351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gold Standard Act of 1900 |
E626770
|
entity |
| Predicate | definedGoldFineness |
P14349
|
FINISHED |
| Object | 0.900 fine |
—
|
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: 0.900 fine | Statement: [Gold Standard Act of 1900, definedGoldFineness, 0.900 fine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definedGoldFineness Context triple: [Gold Standard Act of 1900, definedGoldFineness, 0.900 fine]
-
A.
fineGoldContent
Indicates that one entity specifies the amount or proportion of pure gold contained within another entity.
-
B.
standardGoldContent
chosen
Indicates the specified standard or required amount of gold contained in something, typically as a measure of purity or value.
-
C.
previousGoldPurity
Indicates that one entity represents the gold purity value that applied to another entity at an earlier time or in a prior state.
-
D.
goldDescribedAs
Indicates that something is characterized or referred to using the term "gold" or a gold-related description.
-
E.
nobleMetal
Indicates that the subject is classified as a noble (chemically inert and corrosion-resistant) metal.
- 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_69e2ff28ee3881909c626af002457a4a |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6456608190b94e7c2e2c2a4824 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 18, 2026, 6:07 a.m.