Triple
T4508634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trade dollar |
E101994
|
entity |
| Predicate | higherSilverContentThan |
P57077
|
FINISHED |
| Object | standard silver dollar |
—
|
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: standard silver dollar | Statement: [Trade dollar, higherSilverContentThan, standard silver dollar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: higherSilverContentThan Context triple: [Trade dollar, higherSilverContentThan, standard silver dollar]
-
A.
changedSilverContentOf
Indicates that one entity altered the amount or proportion of silver contained in another entity.
-
B.
silverContentStandard
Indicates the standard or required amount of silver content specified for something, such as a material, product, or item.
-
C.
standardGoldContent
Indicates the specified standard or required amount of gold contained in something, typically as a measure of purity or value.
-
D.
silverWeight
Indicates the weight or mass of an entity measured specifically in silver.
-
E.
higherDenomination
Indicates that one entity represents a monetary value that is greater than the monetary value represented by another entity.
- F. None of above. chosen
Provenance (4 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_69bd43d6251c81909deecce3e6e9d69c |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd570f9b1c8190b52ace855dbf6641 |
completed | March 20, 2026, 2:17 p.m. |
| PD | Predicate disambiguation | batch_69bd5218afb4819087c99e0a1f22e137 |
completed | March 20, 2026, 1:56 p.m. |
| PDg | Predicate description generation | batch_69bd56b3e4c88190a7ade3d0ed0ab606 |
completed | March 20, 2026, 2:16 p.m. |
Created at: March 20, 2026, 1:01 p.m.