Triple
T3842096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bairam Khan |
E93473
|
entity |
| Predicate | regencyStartApprox |
P52344
|
FINISHED |
| Object | 1556 |
—
|
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: 1556 | Statement: [Bairam Khan, regencyStartApprox, 1556]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regencyStartApprox Context triple: [Bairam Khan, regencyStartApprox, 1556]
-
A.
regencyBeganAfter
Indicates that the start of one regency occurred later in time than the start of another regency.
-
B.
includesRegency
Indicates that one entity’s scope, period, or authority encompasses or contains a regency associated with another entity.
-
C.
regency
Indicates that one entity exercises ruling authority on behalf of another, typically when the latter is unable to govern directly (such as due to minority, absence, or incapacity).
-
D.
coRegencyStart
Indicates the point in time when a joint rule or shared reign between two or more authorities begins.
-
E.
hasRegency
Indicates that one entity exercises regency authority or governing power on behalf of another, typically during the latter’s minority, incapacity, or absence.
- 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_69aed96ce578819084ab16e3439976c9 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aeebb397ac81908f74a42a0eeb8682 |
completed | March 9, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69aee74dcecc819098285483ec721b40 |
completed | March 9, 2026, 3:29 p.m. |
| PDg | Predicate description generation | batch_69aeeb828fb08190901d51edbe8bd304 |
completed | March 9, 2026, 3:47 p.m. |
Created at: March 9, 2026, 3:18 p.m.