Triple
T30438407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Massacre of Novgorod |
E774372
|
entity |
| Predicate | mainRiverNearEvent |
P71799
|
FINISHED |
| Object | Volkhov River |
—
|
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: Volkhov River | Statement: [Massacre of Novgorod, mainRiverNearEvent, Volkhov River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainRiverNearEvent Context triple: [Massacre of Novgorod, mainRiverNearEvent, Volkhov River]
-
A.
riverPhenomenon
Indicates a natural event, condition, or process that occurs in or directly affects a river.
-
B.
riverMentioned
Indicates that a river is referenced or discussed in the given context or data.
-
C.
nearbyRiverProject
Indicates that there is a project located close to or associated with a nearby river.
-
D.
mainRiverAssociated
chosen
Indicates that one entity is associated with, or primarily linked to, a particular main river.
-
E.
hasRiverActivity
Indicates that an entity engages in, supports, or is associated with activities occurring on or along a river.
- 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_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_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:08 p.m.