Triple
T32087997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman sestertius |
E819500
|
entity |
| Predicate | majorBronzeReformDate |
P50931
|
FINISHED |
| Object | late 1st century BC |
—
|
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: late 1st century BC | Statement: [Roman sestertius, majorBronzeReformDate, late 1st century BC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorBronzeReformDate Context triple: [Roman sestertius, majorBronzeReformDate, late 1st century BC]
-
A.
lastReform
Indicates the most recent reform or change that was applied to an entity, typically linking the entity to its latest reform event or version.
-
B.
timeOfMajorReforms
chosen
Indicates the specific time period during which significant reforms or major changes took place.
-
C.
redenominationDate
Indicates the date on which a currency or financial instrument undergoes a formal change in its nominal value or unit (redenomination).
-
D.
reformDate
Indicates the date on which a reform, change, or restructuring officially took effect or was implemented.
-
E.
majorAmendmentDate
Indicates the date on which a significant change or revision to something was formally made or took effect.
- 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_69f349004b2481908ce2e50af0d579a8 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fec25f0fc48190b87ab1f9cd1eb0de |
completed | May 9, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69fec079a770819098df7cc3049df954 |
completed | May 9, 2026, 5:04 a.m. |
Created at: May 1, 2026, 12:25 a.m.