Triple
T8227256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corfinium |
E192202
|
entity |
| Predicate | coinageDepicted |
P8603
|
FINISHED |
| Object | Italia personification |
—
|
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: Italia personification | Statement: [Corfinium, coinageDepicted, Italia personification]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coinageDepicted Context triple: [Corfinium, coinageDepicted, Italia personification]
-
A.
denominationDepicted
Indicates that an item visually represents or shows the monetary denomination (value) of a currency.
-
B.
coinageType
Indicates the specific type or category of coinage associated with an entity, such as its denomination, series, or monetary classification.
-
C.
obverseDepiction
chosen
Indicates that one entity is depicted on the obverse (front) side of another, such as the front face of a coin or medal.
-
D.
coinedDenomination
Indicates that an entity created or introduced a particular name, term, or denomination for something.
-
E.
numismaticCategory
Indicates the classification or type of a numismatic object (such as a coin, medal, or token) within a numismatic system or taxonomy.
- 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_69ca82db5b90819085d1ad7c2e27bfcc |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb77fdcb048190868ea4995b020a37 |
completed | March 31, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69cb36af41e081909dee92b9bc4947f1 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:46 p.m.