Triple
T27624663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plague of Amwas |
E696168
|
entity |
| Predicate | contemporaryRuler |
P170650
|
FINISHED |
| Object | Umar ibn al-Khattab |
—
|
NE NERFINISHED |
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: Umar ibn al-Khattab | Statement: [Plague of Amwas, contemporaryRuler, Umar ibn al-Khattab]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contemporaryRuler Context triple: [Plague of Amwas, contemporaryRuler, Umar ibn al-Khattab]
-
A.
contemporaneousRuler
Indicates that two rulers held power during overlapping or the same time periods.
-
B.
contemporaryMonarch
Indicates that two monarchs reigned during overlapping or the same historical time period.
-
C.
currentSovereign
Indicates that one entity is the reigning monarch or ruling sovereign of another entity at the present time.
-
D.
recognizedAsRulersBy
Indicates that certain entities are acknowledged or accepted by others as their legitimate rulers or authorities.
-
E.
coRulership
Indicates a relationship in which two or more entities share authority or power to rule jointly over the same domain or group.
- 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_69ef59092c8881908114ad184248cc46 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f693ffa7908190aa4c451b16df9be6 |
completed | May 3, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69f690eb1e948190aab41a89969519a5 |
completed | May 3, 2026, 12:03 a.m. |
| PDg | Predicate description generation | batch_69f6938244648190a553b532387b812c |
completed | May 3, 2026, 12:14 a.m. |
Created at: April 27, 2026, 2:17 p.m.