Triple
T11675648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mughal Subah of Delhi |
E277483
|
entity |
| Predicate | hasRulingSovereign |
P72321
|
FINISHED |
| Object | Mughal emperor |
—
|
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: Mughal emperor | Statement: [Mughal Subah of Delhi, hasRulingSovereign, Mughal emperor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRulingSovereign Context triple: [Mughal Subah of Delhi, hasRulingSovereign, Mughal emperor]
-
A.
seatOfSovereignty
Indicates that a location serves as the primary center of governing authority or ruling power for a political entity.
-
B.
sovereignGovernment
Indicates that a government possesses ultimate authority and independence over a defined territory, free from external control.
-
C.
hasSovereignPowerOver
Indicates that one entity holds ultimate governing authority or supreme ruling power over another entity.
-
D.
hasSovereignState
Indicates that one entity is the sovereign state that has ultimate authority or jurisdiction over another entity.
-
E.
sovereigntyHolder
chosen
Indicates which entity possesses ultimate governing authority or sovereign control over another entity or territory.
- 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.