Triple
T9857994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | evacuation of Tallinn 1941 |
E239635
|
entity |
| Predicate | tacticsUsedBySoviets |
P30685
|
FINISHED |
| Object | mine sweeping |
—
|
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: mine sweeping | Statement: [evacuation of Tallinn 1941, tacticsUsedBySoviets, mine sweeping]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tacticsUsedBySoviets Context triple: [evacuation of Tallinn 1941, tacticsUsedBySoviets, mine sweeping]
-
A.
SovietAction
Indicates actions, policies, or interventions carried out by the Soviet Union or its authorities toward another entity.
-
B.
strategyUsedByRussians
Indicates a strategy or tactic that is employed or implemented by Russians.
-
C.
SovietOperation
Indicates that an operation, mission, or organized activity is conducted by, on behalf of, or under the authority of the Soviet Union or its institutions.
-
D.
involvedUnitSoviet
Indicates that a Soviet military or organizational unit was involved in a particular event, operation, or action.
-
E.
militaryTacticsUsed
chosen
Indicates that specific military tactics are employed or applied in the context of a particular operation, conflict, or strategic situation.
- 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_69ca84e6493081909cf58c8d42ea856b |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb399bd8081908281d1735cc3909f |
completed | April 2, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69cd1d7621d48190aa6a6f34399514b0 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:35 p.m.