Triple
T11675649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mughal Subah of Delhi |
E277483
|
entity |
| Predicate | usedAdministrativeTitles |
P30521
|
FINISHED |
| Object | subahdar |
—
|
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: subahdar | Statement: [Mughal Subah of Delhi, usedAdministrativeTitles, subahdar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAdministrativeTitles Context triple: [Mughal Subah of Delhi, usedAdministrativeTitles, subahdar]
-
A.
officeHolderMayUseTitle
Indicates that a person who holds a particular office is permitted to use a specified official title.
-
B.
usedInFormalTitleOf
chosen
Indicates that something is employed as part of the official or formal title of an entity.
-
C.
usedAsTitleUntil
Indicates that a particular title was held or used by an entity up to (and including or until) a specified end time.
-
D.
usedAsCourtesyTitleFor
Indicates that one entity serves as a courtesy title or honorific form of address applied to another entity.
-
E.
usedTitleIn
Indicates that one entity employed or referenced another entity as a title in some context.
- 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_69d6aafd0a448190b44da30af8c6c519 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a44504c48190b519765a83ff9c5e |
completed | April 10, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69d88a77e6e88190b7519100bde76575 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:40 p.m.