Triple
T4503102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ottoman kuruş |
E101268
|
entity |
| Predicate | featuredInscription |
P34998
|
FINISHED |
| Object | tughra of the reigning sultan |
—
|
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: tughra of the reigning sultan | Statement: [Ottoman kuruş, featuredInscription, tughra of the reigning sultan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuredInscription Context triple: [Ottoman kuruş, featuredInscription, tughra of the reigning sultan]
-
A.
materialTypicallyInscribedOn
Indicates the material that is most commonly used as the surface or medium on which something is inscribed.
-
B.
mentionedInInscription
Indicates that an entity is referenced or named within a specific inscription or inscribed text.
-
C.
scriptOfInscription
Indicates the writing system or script in which a given inscription is written.
-
D.
isInscribedOn
Indicates that text, symbols, or markings are written, carved, or otherwise permanently placed onto the surface of an object.
-
E.
inscriptionFeature
chosen
Indicates that one entity bears or contains an inscribed element or marking that is treated as a notable feature in relation 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_69bd43d175248190894dc58b5b395c26 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd56fb2bec8190b74b6a49d9475514 |
completed | March 20, 2026, 2:17 p.m. |
| PD | Predicate disambiguation | batch_69bd521671688190bc655d25fa77eba2 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:01 p.m.