Triple
T5511048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al-Sultan al-Azam |
E144564
|
entity |
| Predicate | usedInInscription |
P51076
|
FINISHED |
| Object | imperial farmans of Shah Jahan |
—
|
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: imperial farmans of Shah Jahan | Statement: [Al-Sultan al-Azam, usedInInscription, imperial farmans of Shah Jahan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInInscription Context triple: [Al-Sultan al-Azam, usedInInscription, imperial farmans of Shah Jahan]
-
A.
mentionedInInscription
chosen
Indicates that an entity is referenced or named within a specific inscription or inscribed text.
-
B.
isInscribedOn
Indicates that text, symbols, or markings are written, carved, or otherwise permanently placed onto the surface of an object.
-
C.
materialTypicallyInscribedOn
Indicates the material that is most commonly used as the surface or medium on which something is inscribed.
-
D.
inscriptionUsedWith
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.
-
E.
inscribedOn
Indicates that text, symbols, or markings are written or carved onto the surface of an object.
- 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_69c008f6b5048190a09064116062cf69 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01f4cbc2c819091fcbff5f39ceeb4 |
completed | March 22, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69c01b07bde08190b3933b96bdc70dd5 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:33 p.m.