Triple
T34111347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hindustan region of the Mughal Empire |
E874845
|
entity |
| Predicate | importantProvince |
P180580
|
FINISHED |
| Object | Delhi Subah |
—
|
NE NERFINISHED |
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: Delhi Subah | Statement: [Hindustan region of the Mughal Empire, importantProvince, Delhi Subah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: importantProvince Context triple: [Hindustan region of the Mughal Empire, importantProvince, Delhi Subah]
-
A.
protectedProvince
Indicates that a province is under protection or safeguarding by another entity or authority.
-
B.
traditionalProvince
Indicates that an entity is located in, associated with, or belongs to a historically recognized or customary provincial region rather than a modern administrative unit.
-
C.
isProvincial
Indicates that something belongs to, is characteristic of, or is administered at the level of a province rather than a national or local level.
-
D.
affectedProvince
Indicates that a particular province is impacted or influenced by a specified event, action, or condition.
-
E.
exportProvince
Indicates the province from which goods, services, or resources are exported.
- F. None of above. chosen
Provenance (4 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_69f349a80d4481908527317d43f5c579 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
| PDg | Predicate description generation | batch_69f7431aac148190bb6aac59817c174a |
completed | May 3, 2026, 12:44 p.m. |
Created at: May 1, 2026, 1:53 a.m.