Triple
T21082082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carthaginian shekel |
E519393
|
entity |
| Predicate | hasNumismaticInterest |
P59037
|
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: [Carthaginian shekel, hasNumismaticInterest, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumismaticInterest Context triple: [Carthaginian shekel, hasNumismaticInterest, yes]
-
A.
numismaticSignificance
chosen
Indicates the degree to which something holds importance, value, or relevance within the context of coins, currency, or related monetary artifacts.
-
B.
numismaticCategory
Indicates the classification or type of a numismatic object (such as a coin, medal, or token) within a numismatic system or taxonomy.
-
C.
numismaticEvidence
Indicates that the relationship or claim is supported or illustrated by evidence derived from coins, currency, or related monetary artifacts.
-
D.
numismaticSeries
Indicates a relationship where items are grouped as part of the same numismatic (coin or currency) series, typically sharing a common design, theme, or issuance context.
-
E.
significantCollector
Indicates that an entity plays an important or notable role in collecting items, works, or data related to another entity.
- 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_69e0b506e59c8190849b71ed07929215 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e702db430c81908a1547d8fbe45506 |
completed | April 21, 2026, 4:53 a.m. |
| PD | Predicate disambiguation | batch_69e5dbfcd5e881908f1e4e0d2d237856 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:49 p.m.