Triple
T13596423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Velikiye Luki |
E324832
|
entity |
| Predicate | wwiiEvent |
P23985
|
FINISHED |
| Object | encirclement and battle in 1942–1943 |
—
|
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: encirclement and battle in 1942–1943 | Statement: [Velikiye Luki, wwiiEvent, encirclement and battle in 1942–1943]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wwiiEvent Context triple: [Velikiye Luki, wwiiEvent, encirclement and battle in 1942–1943]
-
A.
WWIIEvent
chosen
Indicates that the event is part of, or directly related to, the historical period and activities of World War II.
-
B.
worldWarIIEventPeriod
Indicates that an event or action occurred during the time period of World War II.
-
C.
sideInWorldWarII
Indicates that an entity was aligned with or participated on a particular side during World War II.
-
D.
WWIITheater
Indicates the geographic or operational theater in which a World War II-related event, action, or entity was involved.
-
E.
statusDuringWorldWarII
Indicates the role, condition, or classification an entity had specifically during the period of World War II.
- 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_69d80769eaf081909d82f44e484d6113 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb0590558819080ccc5874a650b1e |
completed | April 12, 2026, 2:46 p.m. |
| PD | Predicate disambiguation | batch_69dbae18eaf48190809e8b365856cde9 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:49 p.m.