Triple
T697106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Humayun |
E13916
|
entity |
| Predicate | regainedEmpireIn |
P3243
|
FINISHED |
| Object | 1555 |
—
|
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: 1555 | Statement: [Humayun, regainedEmpireIn, 1555]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regainedEmpireIn Context triple: [Humayun, regainedEmpireIn, 1555]
-
A.
regainedPowerAgainIn
Indicates that an entity, having previously lost power, has once more returned to a position of power or control within a specified context or location.
-
B.
regainedPowerIn
chosen
Indicates that an entity has recovered or reestablished its previous level of power, control, or authority within a specified context or domain.
-
C.
hasHistoricalEmpire
Indicates that an entity once possessed, controlled, or was associated with a significant imperial power in the past.
-
D.
historicalEmpireCenter
Indicates that a location served as the primary political or administrative center of a historical empire.
-
E.
independenceRestored
Indicates that a previously dependent or controlled entity has regained its autonomy or self-governance.
- 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_69a493406c408190957eeec9048a8fb6 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a0c8055881909565ebde2be8fd7a |
completed | March 1, 2026, 8:25 p.m. |
| PD | Predicate disambiguation | batch_69a49d2586b081908e052cc5ba1d2685 |
completed | March 1, 2026, 8:10 p.m. |
Created at: March 1, 2026, 7:36 p.m.