Triple
T33409301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khendjer |
E855529
|
entity |
| Predicate | reignStability |
P188455
|
FINISHED |
| Object | politically unstable period |
—
|
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: politically unstable period | Statement: [Khendjer, reignStability, politically unstable period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reignStability Context triple: [Khendjer, reignStability, politically unstable period]
-
A.
reignCertainty
Indicates how certain or uncertain it is that a particular reign or period of rule actually occurred or is correctly assigned.
-
B.
reignStatus
Indicates the status or condition of an entity’s period of rule or governance, such as whether it is ongoing, completed, or otherwise characterized.
-
C.
reignSupportedBy
Indicates that a ruler’s period of rule is backed, upheld, or sustained by a particular person, group, or power.
-
D.
reignWith
Indicates that one entity rules or holds sovereign authority jointly alongside another entity.
-
E.
reignTo
Indicates that one entity exercises ruling authority or governance over another entity or domain during a particular period.
- 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_69f3496f04a08190804e56ac5098b8e4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69fba789c1188190973a919bfe2871f3 |
completed | May 6, 2026, 8:41 p.m. |
Created at: May 1, 2026, 1:36 a.m.