Triple
T28540092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plague Prayers of Mursili II |
E722266
|
entity |
| Predicate | causeOfPlagueExplainedAs |
P175993
|
FINISHED |
| Object | divine punishment |
—
|
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: divine punishment | Statement: [Plague Prayers of Mursili II, causeOfPlagueExplainedAs, divine punishment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfPlagueExplainedAs Context triple: [Plague Prayers of Mursili II, causeOfPlagueExplainedAs, divine punishment]
-
A.
plagueCause
Indicates that one entity is the cause or source of a plague affecting another entity.
-
B.
plagueTransmission
Indicates the way in which plague is passed or spread from one host, vector, or environment to another.
-
C.
plague
Indicates that one entity causes widespread, severe, and often persistent harm, suffering, or affliction to another.
-
D.
plagueEvent
Indicates an event in which a widespread and severe disease outbreak affects a population or area.
-
E.
plagueQuarantine
Indicates that an entity is subjected to or involved in a quarantine imposed in response to a plague or serious epidemic disease.
- 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_69f01a5e42348190b1ffbca26e739c84 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f6db3606808190a80c6e9f5da5b33e |
completed | May 3, 2026, 5:20 a.m. |
| PD | Predicate disambiguation | batch_69f6d82adfa481908a5e196d2e18c73f |
completed | May 3, 2026, 5:07 a.m. |
| PDg | Predicate description generation | batch_69f6db1bc348819097c844f76e2fa4fe |
completed | May 3, 2026, 5:20 a.m. |
Created at: April 28, 2026, 3:34 a.m.