Triple
T19106857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coins of the Ottoman Empire |
E467677
|
entity |
| Predicate | mintSystem |
P18117
|
FINISHED |
| Object | centralized imperial mints |
—
|
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: centralized imperial mints | Statement: [Coins of the Ottoman Empire, mintSystem, centralized imperial mints]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mintSystem Context triple: [Coins of the Ottoman Empire, mintSystem, centralized imperial mints]
-
A.
mint
Indicates the act of creating or issuing something new, typically in an official or authoritative capacity (such as producing new currency or tokens).
-
B.
typeOfMint
Indicates that one entity is a specific kind or variety of mint relative to another entity.
-
C.
marginSystem
Indicates a financial arrangement where securities are bought or held using borrowed funds, with the securities themselves serving as collateral under a defined margin framework.
-
D.
monetarySystemType
chosen
Indicates the type or classification of a monetary system associated with an entity.
-
E.
operatedMintFor
Indicates that one entity managed or ran a minting operation on behalf of 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_69d8dd06a26481908039e2a1bae8c597 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e391245c8190b1393577b61c4f76 |
completed | April 20, 2026, 8:28 a.m. |
| PD | Predicate disambiguation | batch_69e4b9ac41848190afd0f33b42cebe99 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:04 p.m.