Triple
T21324962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bryansk |
E525726
|
entity |
| Predicate | notableWartimeRole |
P16542
|
FINISHED |
| Object | center of partisan movement in World War II |
—
|
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: center of partisan movement in World War II | Statement: [Bryansk, notableWartimeRole, center of partisan movement in World War II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableWartimeRole Context triple: [Bryansk, notableWartimeRole, center of partisan movement in World War II]
-
A.
strategicRoleDuringWar
Indicates that an entity served a particular strategic function or importance during a specific war or armed conflict.
-
B.
notableBattleRole
Indicates the specific role or function an entity played in a notable or historically significant battle.
-
C.
worldWarIIRole
chosen
Indicates the specific role, position, or function an entity had in relation to World War II.
-
D.
preWarRole
Indicates the role, position, or function an entity held before the onset of a specified war or conflict.
-
E.
commanderDuringWorldWarII
Indicates that one entity served as a commander of the other 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_69e0b51b90788190a4dd823d962626da |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e77ed7732c8190a0e7aec6e7cbcef2 |
completed | April 21, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69e6161feea4819091d13bb003363279 |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 4:41 p.m.