Triple
T15004490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | administration of Akbar |
E377673
|
entity |
| Predicate | dividedEmpireInto |
P20121
|
FINISHED |
| Object | subahs |
—
|
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: subahs | Statement: [administration of Akbar, dividedEmpireInto, subahs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dividedEmpireInto Context triple: [administration of Akbar, dividedEmpireInto, subahs]
-
A.
historicallyDividedInto
chosen
Indicates that an entity was separated into multiple distinct parts or regions during a past historical period.
-
B.
wasDividedFromYear
Indicates that an entity began to be separated or partitioned starting from a specified year.
-
C.
territoryDividedAfterDeathInto
Indicates that a person's territory was partitioned into specified parts or among specified successors after their death.
-
D.
hadInternalDivision
Indicates that an entity experienced a split or conflict within its own members, factions, or components.
-
E.
governingEmpire
Indicates that one entity serves as the ruling imperial power that controls or governs another entity.
- 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_69d85cd3a3c881908c71fc424d459c17 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded7322b5c81909089cbbf816e1436 |
completed | April 15, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69de9a6531a88190acde65199a477350 |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:54 a.m.