Triple
T9310862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | aerarium Saturni |
E224001
|
entity |
| Predicate | currencyStored |
P19143
|
FINISHED |
| Object | aerarium in bronze and silver coin |
—
|
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: aerarium in bronze and silver coin | Statement: [aerarium Saturni, currencyStored, aerarium in bronze and silver coin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currencyStored Context triple: [aerarium Saturni, currencyStored, aerarium in bronze and silver coin]
-
A.
currencyOfPurse
chosen
Indicates the type of currency that is contained in or associated with a given purse.
-
B.
currencyDepicted
Indicates that one entity visually represents or shows the image or symbol of a particular currency on it.
-
C.
currencyType
Indicates the specific kind of monetary unit or currency associated with an entity or transaction.
-
D.
currencyGiven
Indicates that one entity transfers or provides money or a monetary unit to another entity.
-
E.
currencyOnboard
Indicates that a particular currency has been enabled, registered, or made available for use within a given system 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_69ca8425f4fc81909c1c586e9a5b7530 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd20ad3b20819092562c30e70a528f |
completed | April 1, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69cc7a61e9a4819096eb014f3791ef2e |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:37 p.m.