Triple
T19245206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Threepenny Beaver |
E481231
|
entity |
| Predicate | hasPhilatelicValue |
P2370
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Threepenny Beaver, hasPhilatelicValue, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPhilatelicValue Context triple: [Threepenny Beaver, hasPhilatelicValue, yes]
-
A.
numismaticSignificance
Indicates the degree to which something holds importance, value, or relevance within the context of coins, currency, or related monetary artifacts.
-
B.
collectibleIn
Indicates that one entity can be collected or obtained within the context, location, or container defined by another entity.
-
C.
collectibleAspect
chosen
Indicates that one entity represents a collectible-related characteristic, feature, or dimension associated with another entity.
-
D.
hadOwnStamps
Indicates that an entity possessed and used its own distinct set of stamps, rather than shared or generic ones.
-
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_69d8e8cd9d1081908a181d02b88b59b8 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fb2c34e88190a338e5a7ba906425 |
completed | April 20, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69e4dd002d00819088b625056edfb74e |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:27 p.m.