Triple
T17892581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imperial Ottoman mints |
E447357
|
entity |
| Predicate | usedInscription |
P27646
|
FINISHED |
| Object | sultan’s tughra |
—
|
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: sultan’s tughra | Statement: [Imperial Ottoman mints, usedInscription, sultan’s tughra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInscription Context triple: [Imperial Ottoman mints, usedInscription, sultan’s tughra]
-
A.
inscriptionUsedWith
chosen
Indicates that a particular inscription is employed together with, or in association with, another object, tool, or context in which it is applied or interpreted.
-
B.
issuedInscription
Indicates that an authority or source formally created and released a specific inscription or written record.
-
C.
isInscribedOn
Indicates that text, symbols, or markings are written, carved, or otherwise permanently placed onto the surface of an object.
-
D.
hasInscriptions
Indicates that an object, surface, or artifact bears written, carved, or engraved inscriptions on it.
-
E.
inscribedFor
Indicates that something is formally written, engraved, or dedicated for a particular recipient or purpose.
- 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_69d8b9f59bd48190a6fc925a855b8bac |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e49d7a855c8190b20bdbf6dcd4fd47 |
completed | April 19, 2026, 9:16 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e9b77c8190bbfb508f28dfacfa |
completed | April 18, 2026, 7:18 p.m. |
Created at: April 10, 2026, 10:19 a.m.