Triple
T30681329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | antoninianus |
E781058
|
entity |
| Predicate | faceValueRelativeTo |
P23870
|
FINISHED |
| Object | 2 denarii (nominal) |
—
|
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: 2 denarii (nominal) | Statement: [antoninianus, faceValueRelativeTo, 2 denarii (nominal)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: faceValueRelativeTo Context triple: [antoninianus, faceValueRelativeTo, 2 denarii (nominal)]
-
A.
faceValueText
Indicates the textual representation of an item's nominal or stated face value (e.g., as printed on a document, currency, or instrument).
-
B.
faceValueUnit
chosen
Indicates the unit of measurement in which the face value of something (such as a financial instrument or item) is expressed.
-
C.
valueRelativeToFlorin
Indicates the monetary value of something expressed in terms of its worth relative to the florin currency.
-
D.
faceValueType
Indicates the type or category of a financial instrument’s face (nominal) value, such as how that value is defined or represented.
-
E.
valueRelativeToMainUnit
Indicates how a value is expressed in relation to a primary or reference unit, such as a main measurement or base quantity.
- 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_69f224a92f54819095499b4d32bd5134 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68b806a1081909fbd1b301a6936a4 |
completed | May 2, 2026, 11:40 p.m. |
| PD | Predicate disambiguation | batch_69f6861170d08190bb98be609d436f84 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:32 p.m.