Triple
T18328965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Winged Liberty Head (Mercury) dime design |
E439083
|
entity |
| Predicate | reverseFigure |
P110337
|
FINISHED |
| Object | fasces |
—
|
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: fasces | Statement: [Winged Liberty Head (Mercury) dime design, reverseFigure, fasces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reverseFigure Context triple: [Winged Liberty Head (Mercury) dime design, reverseFigure, fasces]
-
A.
reverseFeature
Indicates that one feature is the inverse or opposite counterpart of another feature in a given context.
-
B.
reversed
Indicates that the direction or order of a previously defined relationship or sequence between entities is inverted.
-
C.
inverseImage
Indicates the mapping from a set of outputs back to all inputs that are related to those outputs under a given function or relation.
-
D.
reverseInscription
Indicates that one entity is inscribed as the reverse or mirror image of another entity’s inscription.
-
E.
reverseDesignElement
chosen
Indicates that one design element is the reverse or inverse counterpart of another design element.
- 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_69d8b916a2d081909e249e4902f6aad9 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e50aaceb4c81909c4a6b2790602d2e |
completed | April 19, 2026, 5:02 p.m. |
| PD | Predicate disambiguation | batch_69e44fe4ee10819086b4142444fca1f5 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:36 a.m.