Triple
T366994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Half Eagle |
E7981
|
entity |
| Predicate | monetaryMetalRole |
P1838
|
FINISHED |
| Object | full-bodied gold coin |
—
|
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: full-bodied gold coin | Statement: [Half Eagle, monetaryMetalRole, full-bodied gold coin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monetaryMetalRole Context triple: [Half Eagle, monetaryMetalRole, full-bodied gold coin]
-
A.
authorizedCoinMetal
chosen
Indicates that a particular metal is officially approved for use in minting a given coin.
-
B.
monetaryComponent
Indicates that something is a financial element or part of a larger monetary value, structure, or transaction.
-
C.
definedMonetarySystem
Indicates that an authority or entity has established and specified the rules, structure, and characteristics of a particular monetary system.
-
D.
monetaryValue
Indicates the amount of money associated with an entity, event, or transaction.
-
E.
denominationType
Indicates the specific category or kind of denomination associated with an entity, such as its type within a broader classification of denominations.
- 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_69a2e7e880008190a6ad7e06e5d03007 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ebe92c7c8190b49af2b2b461eacc |
completed | Feb. 28, 2026, 1:21 p.m. |
| PD | Predicate disambiguation | batch_69a2e95ede588190998fdf3a6ea90498 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.