Triple
T2324452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The King’s Medal |
E48254
|
entity |
| Predicate | hasObverse |
P8603
|
FINISHED |
| Object | effigy of the reigning King of Sweden |
—
|
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: effigy of the reigning King of Sweden | Statement: [The King’s Medal, hasObverse, effigy of the reigning King of Sweden]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasObverse Context triple: [The King’s Medal, hasObverse, effigy of the reigning King of Sweden]
-
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.
obverseText
Indicates the text that appears on the front (obverse) side of an object, typically a coin or medal.
-
C.
badgeObverseDesign
Indicates the design or imagery that appears on the front (obverse) side of a badge.
-
D.
hasFront
Indicates that an entity possesses or is associated with a front-facing side, surface, or portion.
-
E.
denominationDepicted
Indicates that an item visually represents or shows the monetary denomination (value) of a currency.
- 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_69a88aa308a88190b0b86c011fda7fce |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc685f05481909c863b29d1f6bacd |
completed | March 7, 2026, 6:32 a.m. |
| PD | Predicate disambiguation | batch_69abc5909cc48190aab257313542dc49 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:50 p.m.