Triple
T27189109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swiss 1-franc coin |
E683419
|
entity |
| Predicate | hasObverseDesigner |
P162241
|
FINISHED |
| Object | Albert Walch |
—
|
NE NERFINISHED |
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: Albert Walch | Statement: [Swiss 1-franc coin, hasObverseDesigner, Albert Walch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasObverseDesigner Context triple: [Swiss 1-franc coin, hasObverseDesigner, Albert Walch]
-
A.
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.
-
B.
obverseDepiction
Indicates that one entity is depicted on the obverse (front) side of another, such as the front face of a coin or medal.
-
C.
depictedOnCoinReverse
Indicates that an entity is shown or represented on the reverse (back) side of a coin.
-
D.
type2ObverseRefinementDesigner
Indicates that one design or specification serves as a refined, obverse (reverse-side or counterpart) version of another within a type-2 refinement relationship.
-
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. chosen
Provenance (4 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_69eefad140408190b8586fdebcf9af46 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f625a9e3688190996e628a17d211d0 |
completed | May 2, 2026, 4:26 p.m. |
| PD | Predicate disambiguation | batch_69f620e38aec8190bb184edcdbd6da64 |
completed | May 2, 2026, 4:05 p.m. |
| PDg | Predicate description generation | batch_69f622a8fe7c819096e8a43db263a423 |
completed | May 2, 2026, 4:13 p.m. |
Created at: April 27, 2026, 9:31 a.m.