Triple
T18991737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barber dime |
E464698
|
entity |
| Predicate | obverseLegendPosition |
P122962
|
FINISHED |
| Object | LIBERTY on headband of Liberty |
—
|
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: LIBERTY on headband of Liberty | Statement: [Barber dime, obverseLegendPosition, LIBERTY on headband of Liberty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: obverseLegendPosition Context triple: [Barber dime, obverseLegendPosition, LIBERTY on headband of Liberty]
-
A.
obverseLegendPlacement
chosen
Indicates the spatial placement or arrangement of the legend (inscription or text) on the obverse side of an object, typically a coin or medal.
-
B.
obverseOrReverse
Indicates that two sides or aspects of the same object or item are being related as its obverse (front) and reverse (back).
-
C.
obverseText
Indicates the text that appears on the front (obverse) side of an object, typically a coin or medal.
-
D.
obverseStyle
Indicates the artistic or design style used on the obverse (front) side of an object, such as a coin or medal.
-
E.
obverseDepiction
Indicates that one entity is depicted on the obverse (front) side of another, such as the front face of 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_69d8dd01a56c81909694a128c66b21d7 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d67dee4c8190ac2017ff748ea6aa |
completed | April 20, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69e4a2f88e0c81908cb20f08bf24cd32 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 12:01 p.m.