Triple
T13442539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orel sector |
E320400
|
entity |
| Predicate | closelyLinkedEvent |
P82421
|
FINISHED |
| Object | Soviet counteroffensive after Battle of Kursk |
—
|
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: Soviet counteroffensive after Battle of Kursk | Statement: [Orel sector, closelyLinkedEvent, Soviet counteroffensive after Battle of Kursk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closelyLinkedEvent Context triple: [Orel sector, closelyLinkedEvent, Soviet counteroffensive after Battle of Kursk]
-
A.
closelyAssociatedEvent
chosen
Indicates that one event is strongly related to, connected with, or occurs in close conjunction with another event.
-
B.
isLinkedToEvent
Indicates that an entity has an association or connection with a specific event.
-
C.
laterRelatedEvent
Indicates that one event is temporally related to another by occurring at a later time.
-
D.
associatedEventType
Indicates that one entity is linked to another by the type or category of event with which it is associated.
-
E.
significantConcurrentEvent
Indicates that another event occurs at the same time and is of notable or meaningful importance in relation to the referenced event.
- 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_69d80761e6cc8190a90c844589998ecc |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaee881888190811ddf01bc699864 |
completed | April 12, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69d9a03ce03481908c61094f0cc0c158 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:40 p.m.