Triple
T23498832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman mint |
E571778
|
entity |
| Predicate | currency |
P245
|
FINISHED |
| Object | Roman solidus |
—
|
NE NERFINISHED |
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: Roman solidus | Statement: [Roman mint, currency, Roman solidus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Roman solidus Context triple: [Roman mint, currency, Roman solidus]
-
A.
Byzantine solidus
chosen
The Byzantine solidus was a highly stable and widely circulated gold coin of the Byzantine Empire that served as a key reference currency across the Mediterranean and beyond for centuries.
-
B.
Roman aureus
The Roman aureus was a high-value gold coin of ancient Rome, used primarily for large transactions, savings, and imperial payments.
-
C.
Aqua Antoniniana
Aqua Antoniniana was an ancient Roman aqueduct built to supply water to the Baths of Caracalla in Rome.
-
D.
Roman sestertius
The Roman sestertius was a large bronze coin of the Roman Empire, widely used in everyday transactions and notable for its detailed imperial portraits and propaganda imagery.
-
E.
Follis
The follis was a large bronze coin used in the Byzantine Empire, particularly prominent in the 6th and 7th centuries.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e245b4829881909b77a70e942bbd54 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a7e184ec8190aff3677c9b00a8f2 |
completed | April 29, 2026, 6:40 a.m. |
Created at: April 17, 2026, 6:06 p.m.