Triple
T37756006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sinyavino Heights |
E941113
|
entity |
| Predicate | operationInvolvement |
—
|
GENERATED |
| Object | Soviet attempts to lift the Siege of Leningrad |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operationInvolvement Context triple: [Sinyavino Heights, operationInvolvement, Soviet attempts to lift the Siege of Leningrad]
-
A.
involvedAction
Indicates that an entity participates in, performs, or is otherwise engaged in a specified action or activity.
-
B.
hasBeenInvolvedIn
chosen
Indicates that an entity has participated in, taken part in, or been connected to a particular event, activity, or situation.
-
C.
investigationInvolvement
Indicates that an entity participates in, is associated with, or plays a role in a particular investigation.
-
D.
operationOf
Indicates that one entity is the function, activity, or process carried out by another entity (such as a system, device, or organization).
-
E.
mayBeInvolvedIn
Indicates that an entity has a possible, but not certain, participation or role in a particular event, activity, or situation.
- F. None of above.
Provenance (1 batch)
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_69f76ee1f3a88190834e6c8af99bccc9 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:19 p.m.