Triple
T30438408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Massacre of Novgorod |
E774372
|
entity |
| Predicate | rulerAtTime |
P169433
|
FINISHED |
| Object | Ivan IV of Russia |
—
|
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: Ivan IV of Russia | Statement: [Massacre of Novgorod, rulerAtTime, Ivan IV of Russia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rulerAtTime Context triple: [Massacre of Novgorod, rulerAtTime, Ivan IV of Russia]
-
A.
rulerDuringConstruction
Indicates that a particular person held ruling authority over a place or polity during the time a specific construction project was carried out.
-
B.
rulerDepicted
Indicates that a depicted figure in a representation is the ruler (or sovereign authority) associated with that context or scene.
-
C.
viewOnRuler
Indicates that one entity holds a particular opinion, stance, or perspective regarding a ruler or governing authority.
-
D.
involvesRuler
Indicates that the relationship or action includes or pertains to a ruler as a participating party.
-
E.
recognizedAsRuler
Indicates that one entity is acknowledged or accepted by others as the legitimate ruler or sovereign authority.
- 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_69f22492d2a88190995ce8745d9becaa |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68696b51481908e337f6734102fea |
completed | May 2, 2026, 11:19 p.m. |
| PD | Predicate disambiguation | batch_69f678d2196c8190b9d0d2fcd47cc539 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f67d31cc60819084f64bd056e1ea4d |
completed | May 2, 2026, 10:39 p.m. |
Created at: April 29, 2026, 8:08 p.m.