Triple
T28232987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prussian groschen |
E711803
|
entity |
| Predicate | coinageAuthority |
P13428
|
FINISHED |
| Object | Teutonic Order mint |
—
|
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: Teutonic Order mint | Statement: [Prussian groschen, coinageAuthority, Teutonic Order mint]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coinageAuthority Context triple: [Prussian groschen, coinageAuthority, Teutonic Order mint]
-
A.
coinagePower
Indicates the authority or capacity of an entity to create, issue, or regulate currency or coinage.
-
B.
coinageFeature
Indicates a characteristic, design element, or attribute that is present on or associated with a particular coin or type of coinage.
-
C.
coinIssuer
chosen
Indicates that an entity issues, mints, or is responsible for the creation and release of a particular coin or currency.
-
D.
coinageType
Indicates the specific type or category of coinage associated with an entity, such as its denomination, series, or monetary classification.
-
E.
authorizedCoinMetal
Indicates that a particular metal is officially approved for use in minting a given coin.
- 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_69efb51ece308190b8c269a057e36652 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f6438ba610819081543ffa43c5824c |
completed | May 2, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69f63c6c1a948190b68c0f92c264cc0c |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 10:52 p.m.