Triple
T15522466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Economism in the Russian socialist movement |
E369000
|
entity |
| Predicate | favoredTactic |
P75814
|
FINISHED |
| Object | economic strikes |
—
|
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: economic strikes | Statement: [Economism in the Russian socialist movement, favoredTactic, economic strikes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: favoredTactic Context triple: [Economism in the Russian socialist movement, favoredTactic, economic strikes]
-
A.
tactic
Indicates a strategic method or maneuver employed by one entity to influence, counter, or gain advantage over another in a specific context.
-
B.
hasPrimaryTactic
chosen
Indicates that an entity is associated with its main or most commonly used tactic or method of operation.
-
C.
favored
Indicates that one entity is preferred, supported, or given advantage over others by another entity.
-
D.
describedTactic
Indicates that one entity has provided an explanation or account of a particular tactic used or proposed by another entity.
-
E.
hasCommonTacticOfOpponents
Indicates that two or more entities share the same tactic or strategy used by their respective opponents.
- 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_69d85a1794cc8190b0b428716296e63e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0403543188190abac49d2b9decb89 |
completed | April 16, 2026, 1:49 a.m. |
| PD | Predicate disambiguation | batch_69ded28ab0588190a47a9090d1238707 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 4:04 a.m.