Triple
T14328439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Badshah |
E355273
|
entity |
| Predicate | usedInInscriptionType |
P18110
|
FINISHED |
| Object | royal farmans |
—
|
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: royal farmans | Statement: [Badshah, usedInInscriptionType, royal farmans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInInscriptionType Context triple: [Badshah, usedInInscriptionType, royal farmans]
-
A.
usedInType
chosen
Indicates that something serves as a component, element, or example within a particular type or category.
-
B.
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.
-
C.
hasTypicalInscriptionMethod
Indicates the usual or characteristic method by which inscriptions are applied or created on an object or surface.
-
D.
mentionedInInscription
Indicates that an entity is referenced or named within a specific inscription or inscribed text.
-
E.
isInscribedOn
Indicates that text, symbols, or markings are written, carved, or otherwise permanently placed 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_69d8278fa2108190bc0d0e7939c1eb03 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8c1c3e70819084b6728ac5c18561 |
completed | April 14, 2026, 6:49 p.m. |
| PD | Predicate disambiguation | batch_69de2a9515f4819081aabf251bca5878 |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:13 a.m.