Triple
T17423670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lydia of Croesus |
E423680
|
entity |
| Predicate | coinageInnovation |
P99871
|
FINISHED |
| Object | standardized bimetallic coinage |
—
|
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: standardized bimetallic coinage | Statement: [Lydia of Croesus, coinageInnovation, standardized bimetallic coinage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coinageInnovation Context triple: [Lydia of Croesus, coinageInnovation, standardized bimetallic coinage]
-
A.
coinageFeature
chosen
Indicates a characteristic, design element, or attribute that is present on or associated with a particular coin or type of coinage.
-
B.
coinageType
Indicates the specific type or category of coinage associated with an entity, such as its denomination, series, or monetary classification.
-
C.
coinagePower
Indicates the authority or capacity of an entity to create, issue, or regulate currency or coinage.
-
D.
coinageMotivation
Indicates the reason or purpose motivating the creation or introduction of a particular coinage or monetary issue.
-
E.
banknoteInnovation
Indicates the introduction or development of new features, designs, or technologies in banknotes.
- 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_69d889d88b6081908bada047f5b3ba51 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e44238b418819095c6a013d3ff3b17 |
completed | April 19, 2026, 2:47 a.m. |
| PD | Predicate disambiguation | batch_69e3b02e6cc88190986e85e64ce9383e |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:46 a.m.