Triple
T6548590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | piece of eight |
E151071
|
entity |
| Predicate | standardPurity |
P6859
|
FINISHED |
| Object | high silver fineness |
—
|
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 silver fineness | Statement: [piece of eight, standardPurity, high silver fineness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardPurity Context triple: [piece of eight, standardPurity, high silver fineness]
-
A.
standardPar
Indicates that two entities are parallel and conform to a recognized or defined standard of parallelism.
-
B.
standardGoldContent
Indicates the specified standard or required amount of gold contained in something, typically as a measure of purity or value.
-
C.
standardComposition
Indicates that one entity is composed or constructed according to a recognized or conventional standard defined by another entity.
-
D.
purity
chosen
Indicates that an entity possesses a high degree of cleanliness, integrity, or freedom from contamination, corruption, or mixed elements.
-
E.
standardType
Indicates that one entity is classified as the standard, canonical, or reference type for another entity or context.
- 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_69c687f3fd60819083bfa583e5bcfa71 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ce07332481909a5a7964282eb776 |
completed | March 27, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69c6acf3e3708190b052ec774e607cb7 |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:51 p.m.