Triple
T12513922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indian Princess Head (Type 2) |
E299149
|
entity |
| Predicate | obverseOf |
P8603
|
FINISHED |
| Object | Type 2 gold dollar |
—
|
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: Type 2 gold dollar | Statement: [Indian Princess Head (Type 2), obverseOf, Type 2 gold dollar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: obverseOf Context triple: [Indian Princess Head (Type 2), obverseOf, Type 2 gold dollar]
-
A.
obverseText
Indicates the text that appears on the front (obverse) side of an object, typically a coin or medal.
-
B.
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.
-
C.
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.
-
D.
reversed
Indicates that the direction or order of a previously defined relationship or sequence between entities is inverted.
-
E.
reverseInscription
Indicates that one entity is inscribed as the reverse or mirror image of another entity’s inscription.
- 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_69d6ada4cd388190ae3bbf83ff87057a |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d954b867dc8190af8a70f797e4d133 |
completed | April 10, 2026, 7:51 p.m. |
| PD | Predicate disambiguation | batch_69d954096af88190b6be81b008c82139 |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 8, 2026, 9:57 p.m.