Triple
T36617100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plague of Cyprian |
E903632
|
entity |
| Predicate | primaryTextSource |
P145986
|
FINISHED |
| Object | De mortalitate |
E505202
|
NE 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: De mortalitate | Statement: [Plague of Cyprian, primaryTextSource, De mortalitate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryTextSource Context triple: [Plague of Cyprian, primaryTextSource, De mortalitate]
-
A.
primarySources
Indicates that one entity serves as an original, authoritative source of information or evidence for another entity.
-
B.
primarySourcePassage
Indicates that a passage serves as the main or original source of information or evidence for a given claim, statement, or data item.
-
C.
primaryContentOrigin
chosen
Indicates that one entity is the main or original source from which the content of another entity is derived.
-
D.
primarySourcesDiscussed
Indicates that the primary source materials are examined, analyzed, or discussed in relation to the subject.
-
E.
primarySourceArea
Indicates that something originates from, or is chiefly derived from, a specified source area.
- F. None of above.
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_69f76e6960e4819092047756ceb9a17e |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3a095da0fc81909f74bbe3a45e1702 |
completed | June 23, 2026, 4:19 a.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:11 p.m.