Triple
T32998811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kösem Sultan |
E844304
|
entity |
| Predicate | reignAsValideSultanEnd |
P186391
|
FINISHED |
| Object | 1651 |
—
|
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: 1651 | Statement: [Kösem Sultan, reignAsValideSultanEnd, 1651]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reignAsValideSultanEnd Context triple: [Kösem Sultan, reignAsValideSultanEnd, 1651]
-
A.
reignAsValideSultanStart
Indicates the point in time when an individual begins their tenure as the legitimate reigning sultan.
-
B.
reignAsValideSultanFor
Indicates that one entity serves and exercises authority as the valide sultan (queen mother) during the reign of another entity, typically a ruling sultan.
-
C.
reignAsEmirEnd
Indicates the point in time or event at which an individual's tenure or rule as an emir comes to an end.
-
D.
recognizedAsSultan
Indicates that an entity is acknowledged or accepted by others as holding the status or title of sultan.
-
E.
successorAsValideSultan
Indicates that one entity became the next legitimate or officially recognized sultan after another entity.
- 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_69f3494d99988190b502c68926af2c4d |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69f7cec398ac819081c954a993c323ee |
completed | May 3, 2026, 10:40 p.m. |
Created at: May 1, 2026, 1:22 a.m.