Triple
T3660901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silas |
E77644
|
entity |
| Predicate | perpetrates |
P698
|
FINISHED |
| Object | murders of Priory of Sion members |
—
|
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: murders of Priory of Sion members | Statement: [Silas, perpetrates, murders of Priory of Sion members]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: perpetrates Context triple: [Silas, perpetrates, murders of Priory of Sion members]
-
A.
perpetuates
Indicates that one entity causes a state, condition, or situation involving another entity to continue or persist over time.
-
B.
persecutes
Indicates that one entity persistently harasses, oppresses, or inflicts suffering on another, often in an unjust or hostile manner.
-
C.
perpetratedBy
chosen
Indicates that an action, event, or wrongdoing was carried out or caused by a particular agent or entity.
-
D.
promulgates
Indicates the act of formally declaring, publishing, or putting a law, rule, or doctrine into official effect.
-
E.
conducts
Indicates that an entity organizes, directs, or carries out an activity, operation, or process involving another entity.
- F. None of above.
Provenance (3 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_69ad85dfc4dc8190a441864202ab2a7a |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc3d6fa188190a6db5bdae7083573 |
completed | March 8, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69adb847e9d881909dad2ffd0f3b6c15 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:25 p.m.