Triple
T23689715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Follis |
E585262
|
entity |
| Predicate | typicalObverseDesign |
P8603
|
FINISHED |
| Object | bust of the emperor |
—
|
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: bust of the emperor | Statement: [Follis, typicalObverseDesign, bust of the emperor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalObverseDesign Context triple: [Follis, typicalObverseDesign, bust of the emperor]
-
A.
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.
-
B.
obverseDesignIntroduced
Indicates that a particular obverse design (front side of an item, typically a coin or medal) was first put into official use at a specified time.
-
C.
depictedOnCoinReverse
Indicates that an entity is shown or represented on the reverse (back) side of a coin.
-
D.
badgeObverseDesign
Indicates the design or imagery that appears on the front (obverse) side of a badge.
-
E.
obverseStyle
Indicates the artistic or design style used on the obverse (front) side of an object, such as a coin or medal.
- 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_69e249037ce0819088b149608e98f685 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b5c0a218819096c2d174b004c47d |
completed | April 29, 2026, 7:39 a.m. |
| PD | Predicate disambiguation | batch_69f155d5265881908e43a9696b6a6d0f |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 6:52 p.m.